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 of behavioral disclosure. While 'Adds' indicates a write operation, the description lacks critical details such as error handling behavior for partial failures, whether the operation is idempotent, or what the tool returns upon completion.

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 efficient sentence (provided in English and Japanese), immediately stating the tool's purpose without filler. However, given the lack of annotations and the nested complexity of the results parameter, it borders on underspecified 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?

With 100% schema coverage clearly defining all input parameters, the description meets minimum viability. However, as a mutation tool with no output schema, no annotations, and no mention of error handling or success indicators, it has clear gaps that leave an agent without full operational 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?

Schema description coverage is 100%, with all parameters including nested fields (statusId, assignedtoId, elapsed) fully documented with types and descriptions. The description mentions 'multiple test cases' which aligns with the results array structure, but adds no additional semantic context beyond what the schema already provides, 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 states 'Adds test results for multiple test cases in a test run', providing a specific verb (Adds), resource (test results), and scope (multiple test cases). The explicit mention of 'multiple' effectively distinguishes this tool from sibling `addResultForCase` which handles single cases.

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 batch usage through the word 'multiple', suggesting it is designed for bulk operations. However, it does not explicitly state when to use this versus `addResultForCase` for single cases, nor does it mention prerequisites such as the runId needing to exist.

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