TestRail MCP Server

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

No annotations are provided, so the description carries full disclosure burden. It indicates a mutation via 'Adds' but omits critical behavioral details: error handling for missing entries, idempotency, side effects on existing runs, or return value structure.

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 extremely brief (one sentence plus translation) with zero redundant text. However, for a mutation tool with 8 parameters and no output schema, this extreme brevity slightly underserves the complexity despite being efficient.

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 8 parameters, no annotations, no output schema, and mutation behavior, the description provides minimum viable information to identify the tool's function but leaves significant gaps regarding operational behavior, error conditions, and return values.

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 8 parameters. The description adds no supplemental parameter context (e.g., relationship between includeAll and caseIds, or configIds semantics), meriting the baseline score 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 specific action (Adds) and target resource (new test run to existing plan entry), effectively distinguishing it from siblings like addRun (standalone runs) and addPlanEntry (creating entries vs adding runs to them).

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?

While the description specifies the target is an 'existing plan entry' providing implicit context, it lacks explicit when-to-use guidance, prerequisites (e.g., plan entry must exist), or comparisons to alternatives like addRun for standalone test runs.

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