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. While 'Retrieves' implies read-only access, the description omits behavioral details like pagination limits, rate limiting, error handling for invalid runIds, or the distinction between 'tests' (instances) and 'cases' (templates) in TestRail terminology.

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 bilingual description (English/Japanese) is efficiently structured with zero waste—front-loaded with the verb and immediately scoping to the test run context in minimal space.

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?

Without an output schema, the description partially compensates by indicating a 'list' return type. However, given the complex sibling ecosystem (tests vs cases vs results), it should clarify what constitutes a 'test' in this context.

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?

With 100% schema description coverage, the schema adequately documents all three parameters including pagination hints. The description adds no parameter-specific semantics, meeting the baseline for high-coverage schemas.

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 the action ('Retrieves') and resource ('list of tests for a test run'), distinguishing it from siblings like 'getTest' (singular), 'getCases' (templates), and 'getResultsForRun' (results).

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 description implies usage by mentioning 'test run' context, but provides no explicit when-to-use guidance, pagination strategy, or contrast with 'getTest' (singular) despite having pagination parameters.

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