Search the officer roster by whole-word name, state code, or agency slug.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "search_officers"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| page | No | ||
| state | No | ||
| agency | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral disclosure, but it only states the search modes. It does not mention result format, pagination behavior, whether the query is case-insensitive or exact, or how multiple supplied criteria are combined.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, scannable sentence that front-loads the verb and resource, then lists the search dimensions. There is no redundant wording or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema and no annotations, so the description should convey result shape and calling conventions. It provides no pagination semantics, no response format, and no handling for the defaulted optional parameters, leaving an agent uncertain about what the tool returns.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Given 0% schema description coverage, the description compensates partially by clarifying that q is a name, state is a state code, and agency is an agency slug, and that name matching is whole-word. However, the page parameter is not explained at all, leaving a coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a search verb, the target resource ('officer roster'), and the accepted search criteria (whole-word name, state code, agency slug). It does not explicitly distinguish this tool from the sibling officer_lookup, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to prefer this tool over alternatives like officer_lookup or search_meetings. The description implies use for officer-roster searches but provides no exclusions, fallbacks, or comparison with sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.