# Choose exact task filters for an MCP read

Illustrative planning brief; no automatic product import.

Illustrative request: show blocked work owned by one named teammate in a specified project.

## Decision

Resolve names and apply supported attributes; clarify ambiguity rather than choosing a convenient match.

## Owned work

- Preserve each constraint
  - Owner role: Agent
  - Acceptance evidence: The requested status, owner and project remain explicit.
- Resolve names safely
  - Owner role: User
  - Acceptance evidence: Ambiguous candidates are clarified before a scoped filter is interpreted.
- Assess coverage
  - Owner role: Reviewer
  - Acceptance evidence: Limits and unavailable conditions are stated rather than silently omitted.

## Workflow

1. Write the requested attributes separately from topic wording.
2. Use the structured tool contract and verified name resolution.
3. Explain any unsupported constraint and coverage limit.

## Judgment

Names can be ambiguous. A returned short list does not establish complete workspace coverage.


## Filled illustrative decision

In the synthetic request, two workspace members share a similar display name. The operator resolves the intended member using approved membership evidence and then scopes the task query to the agreed project and state. A broad semantic match is kept as a candidate until identity is confirmed.


## Scope conditions

- Requested set / Status/owner/project constraints preserved / Reject a silently broadened or narrowed answer
- Name resolution / Exact or unique supported match / Ask about ambiguous candidates
- Coverage / Tool limits and result boundary understood / Label partial or unavailable evidence


## Workflow questions

### Can an agent choose the first matching person?

No. Clarify ambiguous identity before attributing work.

### What if a filter is unsupported?

State the limitation and discuss an explicit alternative instead of pretending the condition was applied.

## Product connection

Use the TeamBoost MCP exact-filter example for an attribute question, with semantic retrieval reserved for a separate meaning-based question.

Confirm account availability before adopting this manual outline.