TestRail MCP Server

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

No annotations provided, so description carries full burden. Claims 'all' results but doesn't explain pagination behavior (limit/offset), doesn't disclose whether operation is read-only/safe, and omits what happens if runId doesn't exist.

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?

Extremely concise single sentence front-loaded with purpose. The Japanese translation adds no value for English-speaking agents but doesn't significantly detract. Could be more informative rather than just brief.

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?

With 5 parameters including pagination controls and no output schema, the description is too minimal. Should mention pagination necessity for large runs and contrast with siblings to aid selection.

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%, so schema already documents all 5 parameters (runId, limit, offset, statusId, defectsFilter). Description adds no additional semantic context beyond implying pagination through 'all' results, warranting baseline score.

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?

States specific verb ('Retrieves') + resource ('test results') + scope ('for a test run'), distinguishing it from sibling 'getResultsForCase' which targets specific cases. However, it doesn't clarify when to prefer this over the broader 'getResults' sibling.

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?

Provides no guidance on when to use this tool versus 'getResults' or 'getResultsForCase', nor does it mention pagination requirements for large result sets despite having limit/offset parameters.

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