Retrieve all available symbols from TestMonitor using this tool. Use it to fetch the complete symbol collection for project data and test management tasks.
Get all symbols. Retrieve all available symbols.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing about result size, ordering, or scope, contributing no behavioral context beyond the annotations.
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?
Two sentences that say exactly the same thing; the second is pure redundancy. Short, but the sizing comes from under-specification rather than disciplined concision.
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?
For a no-parameter list tool with no output schema, the description still leaves the central question unanswered: what is a 'symbol' in this resource model. Sibling tools at least name concrete domains (issues, risks, test runs), while this one stays opaque.
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 tool takes zero parameters, so schema coverage is moot and the baseline of 4 applies. Nothing in the description is needed to clarify non-existent parameters.
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 restates the tool name with no added meaning: 'Get all symbols. Retrieve all available symbols.' It never identifies what a 'symbol' is in this API's domain, and with a large family of sibling get_*_collection tools it offers no differentiation.
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?
There is no guidance on when to use this tool, when not to, or what alternative exists. The two sentences are interchangeable restatements rather than usage conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.