enquiry_describeRead first. States plainly what submit_enquiry does on Fax Line Index: 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 of behavioral disclosure, and it succeeds. It explains that the tool returns a plain-language description, explicitly states that no purchase or payment occurs, clarifies that no quote is guaranteed, and lists the return contents: 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 three sentences with no filler. The imperative 'Read first' is front-loaded, the core purpose appears immediately, and the remaining sentences efficiently add scope, expectations, and return-value details without repetition.
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 documentation tool with no output schema and no annotations, the description is complete. It tells the agent what the tool does, what it does not do, and what information it returns, leaving no important gap for invoking or interpreting the tool.
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 and 100% schema coverage by vacuity, so there is no parameter meaning for the description to add. The description instead focuses on what the tool returns, which is the only semantic information an agent needs for a parameterless documentation 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 states clearly that this tool explains what submit_enquiry does, using the specific verb 'States plainly' and naming the resource it documents. It also distinguishes itself from submit_enquiry by emphasizing that nothing is bought, ordered, or paid, and that it returns information rather than performing the 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 'Read first' clearly signals that this tool should be used before submit_enquiry, and the description provides helpful context about what to expect. It does not explicitly name alternative tools or provide when-not-to-use conditions, but the usage context is clear enough for an agent to recognize this as the pre-submission explainer.
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 purpose: schema, provenance, search, exact match, stats, top, compare, describe, fields, and submit. No overlap or ambiguity between dataset exploration and enquiry submission tools.
All tools follow a consistent snake_case pattern with clear prefixes (dataset_ and enquiry_) and descriptive suffixes (columns, search, stats, submit). Naming is uniform and predictable.
10 tools is well-scoped for a server that handles dataset exploration (7 tools) and an enquiry workflow (3 tools). Each tool earns its place and covers necessary operations without redundancy.
The dataset tools cover schema, provenance, search, exact match, statistics, top values, and comparison, while the enquiry tools cover description, field schema, and submission with confirmation. No obvious gaps for the stated purpose.