enquiry_describeRead first. States plainly what submit_enquiry does on Pub Mortgage Calculator: 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 burden. It discloses the non-transactional nature of the enquiry (nothing bought, ordered, or paid; no guaranteed quote; free) and what the description returns. It stops short of explicitly stating that this tool itself is read-only, but that is strongly implied by describing rather than performing the action.
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 well-structured and front-loaded with the 'Read first' instruction, then explains the core behavior and return contents in a compact set of sentences. It is slightly meta in phrasing but every sentence contributes useful information.
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, no-output-schema describe tool, the description is adequately complete: it explains what the underlying submit_enquiry flow does and what information the description will contain. No critical details needed to use the tool correctly 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 takes zero parameters, so no additional parameter semantics are needed. The description appropriately focuses on behavior and return content rather than input details.
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 explains what submit_enquiry does on Pub Mortgage Calculator, including that it starts a human enquiry, involves no purchase or payment, and guarantees no quote. This is a specific verb+resource description and is distinguishable from siblings like submit_enquiry and calculator_describe.
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 'Read first' is an explicit usage instruction, telling the agent to consult this tool before using submit_enquiry. It does not list alternatives or exclusions, but for a describe-style tool the guidance is sufficient and clear.
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 targets a distinct concern: calculate runs the calculator, calculator_describe documents its inputs/outputs, enquiry_describe explains the submission flow, enquiry_fields provides the schema, and submit_enquiry performs the two-step submission. There is no real overlap in purpose despite some similar naming.
The naming convention is inconsistent: some tools are verb-first (calculate, submit_enquiry) while others are noun-first (calculator_describe, enquiry_describe, enquiry_fields). The mixed ordering and inconsistent verb/noun placement make the tool names harder to predict.
Five tools is well-scoped for a focused mortgage calculator and enquiry submission server. Each tool fills a necessary role, and there is no bloat or redundancy.
The surface covers the full workflow: understanding the calculator, executing it, reading the enquiry process, fetching the required fields, and submitting with two-step consent. There are no obvious missing operations for the stated purpose.