compare_optionsThe options in the UK garage management software for MOT stations and workshops comparison (name, what it is best for, tags), optionally filtered by a tag value.
| Name | Required | Description | Default |
|---|---|---|---|
| filterKey | No | ||
| filterValue | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses one behavioral trait: the result can be optionally filtered by a tag value, which implies a query/read operation. It does not explicitly confirm read-only behavior, what happens without a filter, or how the returned options are structured beyond the listed fields.
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 one compact sentence with no filler and front-loads the domain and resource. However, the noun-phrase grammar is structurally awkward and reads more like a definition than an instruction, which reduces clarity.
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?
The tool is simple (two optional parameters, no output schema), and the description gives the main data fields plus the optional-tag filter. It remains incomplete because filterKey is left unexplained, so an agent cannot confidently construct a filtered call without guessing.
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 coverage is 0%, so the description must compensate for the undocumented filterKey and filterValue parameters. It partially does by explaining that filtering is by a 'tag value' and mentioning tags as an attribute, but it never defines what filterKey is or how the key and value combine.
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 identifies a concrete resource ('options') in a specific domain ('UK garage management software for MOT stations and workshops comparison') and lists its fields (name, what it is best for, tags). It is not a tautology, but it is written as a noun phrase rather than a clear verb statement like 'lists' or 'returns', and it does not explicitly differentiate from sibling tools such as compare_criteria or compare_table.
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 gives no guidance on when to use compare_options versus the sibling tools. The word 'comparison' weakly implies a role in the comparison workflow, but there are no conditions, exclusions, or alternative tool names provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The compare_* tools are clearly distinct: criteria, options, and the full table each target a different aspect of the comparison data. The enquiry_* tools also separate explanation, schema, and submission. No two tools appear to do the same thing.
All names use snake_case and are grouped into compare_ and enquiry_ prefixes, which is readable and predictable. The main deviation is enquiry_describe and enquiry_fields placing the noun first, while submit_enquiry and compare_* follow verb_first, but this is minor and does not cause confusion.
Six tools is a well-scoped set for this server: three tools cover the comparison table surface and three cover the enquiry flow. Every tool earns its place with no redundant or filler tools.
The comparison domain is fully covered: users can list criteria, list options, and view the full criteria-by-option table. The enquiry flow is also complete with an explainer, field schema, and a two-step submit process including consent and confirmation.