compare_optionsThe options in the Letting agent and property management systems used by UK agencies 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?
No annotations are provided, so the description carries the behavioral burden. It usefully discloses that results include name, best-for, and tags, and that results can be filtered by a tag value. However, it does not state default behavior when no filter is provided, what filterKey means, or confirm the operation has no side effects.
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 a single sentence but with an awkward, overly long noun phrase: 'Letting agent and property management systems used by UK agencies comparison.' The main point is buried, and the lack of a lead verb makes it harder to parse. It could be more direct and front-loaded.
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 two undocumented parameters, no output schema, no annotations, and no differentiation from siblings, the description leaves too much to inference. Missing context includes the meaning of filterKey, the default result set, and the relationship to other comparison-related tools.
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 0%, and neither filterKey nor filterValue has any schema documentation. The description only mentions filtering by 'a tag value,' which likely maps to filterValue, but it leaves filterKey completely unexplained. This is insufficient compensation for the missing parameter metadata.
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 names the resource ('options' in the letting-agent comparison) and lists attributes (name, best-for, tags), which gives some clarity. However, it lacks an explicit verb such as 'list' or 'retrieve' and reads as a noun-phrase label rather than a complete tool instruction. It does not clearly distinguish itself from sibling tools like compare_table or compare_criteria.
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 about when to use compare_options versus its siblings. The phrase 'optionally filtered by a tag value' describes a filtering option within the tool, not a condition for choosing this tool over alternatives.
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 six tools split cleanly into comparison data (criteria, options, table) and enquiry workflow (describe, fields, submit). Each tool targets a distinct resource or stage, so an agent should not confuse them.
Names are all lowercase snake_case and grouped by domain: compare_* for comparison and enquiry_* / submit_enquiry for the enquiry flow. However, enquiry_describe and enquiry_fields use noun_first naming while submit_enquiry uses verb_first, so there is a minor structural inconsistency.
Six tools is well-scoped: three for viewing the comparison and three for handling the enquiry lifecycle. There is no redundancy and every tool serves a necessary purpose.
The comparison side exposes criteria, options, and the full values table, while the enquiry side covers explaining the action, describing fields, and submitting with a two-step confirmation. This fully supports the server's stated site purpose with no obvious dead ends.