enquiry_describeRead first. States plainly what submit_enquiry does on Subsidence Survey Cost: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 burden and does well: it discloses that nothing is bought, ordered, or paid for, that no quote is guaranteed, and that the tool returns who receives details, consent wording, and confirmation method. The read-only nature is implied by 'Read first' and 'States plainly'.
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 compact and front-loaded with 'Read first.' It conveys the purpose, key behavioral caveats, and return content in three sentences without significant waste, though the title is somewhat wordy.
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 informational tool with no output schema, the description is sufficiently complete: it tells the agent what the tool explains, what is not involved, and what will be returned. No critical invocation details are missing.
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 the baseline of 4 applies. The description appropriately focuses on what the tool returns rather than parameter usage, since no parameters exist to document.
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 that this tool is a read-first explanation of what submit_enquiry does: it starts an enquiry with human providers, not a purchase or guaranteed quote. This distinguishes it from the sibling submit_enquiry action and gives the agent a clear reason to call it.
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?
'Read first' explicitly tells the agent to use this before acting on submit_enquiry. It does not explicitly contrast with enquiry_fields, but the context that this explains submit_enquiry's behavior is clear enough for routing.
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.
Each tool has a clearly distinct responsibility: enquiry_describe explains the process, enquiry_fields provides the schema, and submit_enquiry performs the submission. There is no meaningful overlap or risk of selecting the wrong tool.
The names are readable and use the 'enquiry' domain consistently, but the pattern is mixed: enquiry_describe and enquiry_fields are object-first, while submit_enquiry is verb-first. This is understandable but not a consistent verb_noun convention.
Three tools is well-scoped for this server's purpose: orientation, field discovery, and submission. Each tool earns its place and there is no unnecessary surface area.
The enquiry lifecycle is fully covered: the agent can learn the process, fetch all required fields, validate and submit with consent, and handle the two-step confirmation. No obvious dead ends or missing operations exist for the stated domain.