enquiry_describeRead first. States plainly what submit_enquiry does on Compare Call Answering: 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 full disclosure burden. It states what the tool returns (who receives details, consent wording, confirmation method) and clarifies key caveats about the underlying submit_enquiry flow: no payment, free, and no guaranteed quote. It does not explicitly assert that this describe tool is side-effect-free, but the descriptive nature and 'Read first' directive sufficiently imply a read-only 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 compact and front-loaded: a one-word directive, a purpose statement, key caveats, and a return-content sentence. Every sentence serves a distinct purpose, and there is no filler in the description itself.
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 simple 0-parameter informational tool with no output schema, the description is complete: it explains what the tool does, what important caveats the caller should know, and what information it returns. The 'Read first' instruction also supplies the placement within the tool flow.
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?
This tool has zero parameters, so the schema fully covers parameter semantics; the 0-parameter baseline is 4. The description appropriately adds no redundant parameter 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 names the exact resource it explains (submit_enquiry) and the specific context (Compare Call Answering), making clear that this tool provides a plain-language explanation rather than performing the enquiry action. The title reinforces the distinction by emphasizing that no purchase or guaranteed quote is involved, separating it from the action-oriented sibling submit_enquiry.
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' clearly signals that this tool should be used as a prerequisite before entering the enquiry flow. It does not explicitly enumerate exclusions or contrast with siblings like enquiry_fields or compare_options, but the usage context is clear enough for an agent.
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 three compare_* tools are the only potentially overlapping group, but their descriptions clearly separate criteria, options, and the full value table. The enquiry_* tools are distinct and even include a read-first descriptor to avoid misuse.
Most names follow a verb_noun style such as compare_criteria and submit_enquiry, but enquiry_describe and enquiry_fields are noun-first, creating mixed conventions within the enquiry cluster. The names remain readable and the prefix groups help navigation.
Six tools is well-scoped for a comparison site: three cover browsing the comparison data and three cover the enquiry flow. Each tool has a clear reason to exist without redundancy.
The comparison side offers criteria, options, and a full matrix, while the enquiry side covers description, field schema, and a two-step validated submission with consent and confirmation. There are no obvious dead ends or missing lifecycle steps for this narrow domain.