Skip to main content
Glama

What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)

enquiry_describe

Read first. States plainly what submit_enquiry does on Lead generation for roofing: it starts an enquiry with Lead generation for roofing, whose team reads it and replies 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "enquiry_describe"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does well: it states nothing is bought, ordered or paid, that no quote is guaranteed, and that the interaction is free — the commercial traits an agent most needs. It also discloses the return contents (recipient, consent wording, confirmation method) but says nothing about auth, rate limits, or whether the returned wording must be surfaced verbatim.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded 'Read first' is good, and the cost/guarantee disclaimers are useful. However, 'Lead generation for roofing' is repeated verbatim within the same sentence and the opening clause duplicates what the title already says, so a portion of the text does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-annotations, no-output-schema tool, the description covers the essentials: what it returns and the key non-obvious guarantees (free, no purchase, no guaranteed quote). It could add whether calling this is mandatory before submit_enquiry or merely recommended, but nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter hints are introduced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this is an informational/descriptive read tool that explains the enquiry flow and returns the recipient, consent wording, and confirmation method. It names the sibling action tool submit_enquiry explicitly, so an agent can separate 'describe' from 'submit'. The only friction is that two of the three sentences describe what submit_enquiry does rather than this tool, so the reader must attribute them correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Read first' is an explicit ordering directive tied to the sibling submit_enquiry, telling the agent to call this before submitting. It does not state any exclusion case (e.g., skip if already submitted) or what to do if the returned terms are unacceptable, so guidance is strong but not complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources