TestRail MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states that it retrieves data without mentioning pagination behavior, rate limits, or return format. While 'Retrieves' implies a read-only operation, the description does not confirm safety properties or explain how the limit/offset parameters affect result sets. The lack of output schema compounds this gap.

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 consists of a single concise sentence provided in both English and Japanese, with no redundant or wasteful content within each language version. Every word serves to identify the tool's core function. However, given the complexity of eight parameters and no annotations, the description is arguably too brief rather than optimally concise.

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?

While the input schema is fully documented at 100% coverage, the description lacks guidance on the return value structure and pagination behavior given the absence of an output schema. For a tool with eight filtering and pagination parameters, the description should provide usage context or behavioral notes. It minimally suffices but leaves significant gaps for agent understanding.

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?

The input schema has 100% description coverage, with each parameter like 'projectId' and 'createdAfter' already clearly documented in the schema itself. The description adds no additional parameter semantics, examples, or validation rules beyond what the schema provides. With complete schema coverage, this meets the baseline expectation.

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 tool 'Retrieves all test runs for a specified TestRail project,' providing a specific verb and resource scope. It implicitly distinguishes from the singular sibling `getRun` by specifying 'all' test runs. However, it does not explicitly differentiate from related siblings like `getTests` or `getResultsForRun` which handle different TestRail entities.

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 provides no guidance on when to use this tool versus alternatives such as `getRun` for retrieving a single specific run. It does not mention prerequisites like project permissions or suggest when to apply the various filtering parameters (createdBy, milestoneId, etc.). No exclusions or alternative workflows are documented.

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