TestRail MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states the read operation ('Retrieves') but fails to disclose pagination behavior, filtering logic, error handling (e.g., case not found), or the structure/format of the returned test results.

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?

The description is a single efficient sentence (presented bilingually) with the action verb front-loaded. There is no redundant or wasted text; every word serves to clarify the tool's scope and purpose.

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?

Given the 6 well-documented input parameters and lack of output schema, the description adequately covers the retrieval purpose but leaves a gap regarding the return value structure and content. It meets minimum viability but does not compensate for the missing output schema with descriptive text.

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?

Schema description coverage is 100%, establishing a baseline of 3. The description reinforces the required parameters by mentioning 'test case' and 'test run', but adds no additional semantic context for the optional filtering parameters (statusId, defectsFilter) or pagination controls beyond what the schema already provides.

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 uses a specific verb ('Retrieves') with clear resource ('test results') and scope ('for a specific test case in a test run'). This effectively distinguishes it from siblings like 'getResults' (general) and 'getResultsForRun' (bulk retrieval for entire run).

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?

The scope 'specific test case in a test run' implies when to use this tool (targeted retrieval) versus bulk alternatives, but there is no explicit guidance naming alternatives or stating when NOT to use it. The agent must infer the distinction from the parameter schemas.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.