enquiry_describeRead first. States plainly what submit_enquiry does on Probate Costs: 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 provided, the description carries the full disclosure burden and does so well: it states that the linked action starts an enquiry with human providers, involves no purchase or payment, is free, and does not guarantee a quote. It also lists what information is returned, including recipients, consent wording, and confirmation method.
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 the 'Read first' directive and the core purpose. Some minor redundancy exists with the title's 'not a purchase, not a guaranteed quote' phrasing, but each sentence still earns its place.
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 0-parameter tool with no output schema, this description is complete: it tells the agent when to use it, what it explains, what behavioral caveats exist, and what information is returned. An agent would have enough context to invoke it correctly and understand the result.
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 input schema contains zero properties, so there are no parameter semantics to document. The description instead adds value by explaining what the tool conveys and returns, which is the relevant semantic content for this 0-parameter informational tool.
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 'States plainly what submit_enquiry does on Probate Costs', giving it a specific verb, resource, and scope. It also distinguishes itself from the submit_enquiry sibling by framing itself as the explanatory 'read first' tool rather than the action-taking one.
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 opening directive 'Read first' explicitly tells the agent to consult this tool before proceeding, likely before calling submit_enquiry. It does not explicitly contrast with enquiry_fields, but the ordering guidance is clear enough for basic 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 role: one explains the enquiry process, one provides the field schema, and one submits the enquiry. There is no overlap or ambiguity about which tool to call.
All names are lowercase and snake_case, but the pattern is mixed: two tools begin with 'enquiry_' and one begins with the verb 'submit'. This is readable but not as predictable as a consistent verb_noun or noun_verb convention.
Three tools is well-scoped for the stated purpose of enquiring about Probate Costs. Each tool earns its place: describe, fields, and submit form a complete minimal workflow.
The tool set fully covers the enquiry lifecycle: orientation, schema discovery, submission with validation, user confirmation, and final submission. There are no obvious missing operations for the domain.