get_gear_collectionsGet all gear collections that group equipment used together, such as running kits or bike components, to understand your gear setup.
Get all gear collections. Collections group gear items that are used together (e.g., running kit, bike components).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v4.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds domain context about collections grouping gear items but does not disclose additional behavioral traits such as ordering, pagination, authentication, or return shape.
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 two short sentences, front-loads the action, and includes a helpful example. Every word earns its place, with no repetition of the tool name or title.
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 zero-parameter, read-only list tool, the description is fully adequate. It explains what the tool returns and why collections matter, while annotations cover the safety semantics. There is no missing essential context for correct invocation.
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 has zero parameters, so there is no semantic burden on the description. Schema coverage is trivially 100%, and the description adds relevant domain context without needing to explain parameter behavior.
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 and resource: 'Get all gear collections.' It also explains what collections are with concrete examples, which distinguishes this from sibling tools like get_gear_collection (singular) or get_all_gear (gear items, not collections).
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 phrase 'Get all gear collections' implies use for retrieving the full set of collections, and the sibling list includes get_gear_collection for a single one. However, the description does not explicitly state when to use this tool versus alternatives or provide any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.