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 SEO Devon: it starts an enquiry with SEO Devon, 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

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the important behavioral traits: nothing is bought, ordered or paid, no quote is guaranteed, and the interaction is free. It also reveals what the call returns (recipient details, consent wording, confirmation method). It does not explicitly say the call is read-only/side-effect-free for the caller, which would have completed the safety picture.

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

Conciseness4/5

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

The imperative 'Read first.' is front-loaded and the rest is organized as: what the enquiry is, what it is not, and what is returned. The only waste is the near-synonym triad 'bought, ordered or paid', which repeats one idea three times.

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?

With no output schema, the description must say what comes back, and it does: recipient of the details, consent wording, and confirmation method. For a zero-parameter informational tool this is nearly complete; only the boundary against enquiry_fields 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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no invented arguments and instead spends its words on return content.

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 names a specific function: it returns documentation about submit_enquiry — who receives enquiries, the consent wording, and how a person confirms. That is far more specific than the title alone. It falls short of a 5 because it never distinguishes itself from the sibling enquiry_fields, so an agent must guess which descriptive tool to open.

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 explicit ordering guidance that tells the agent to call this before submit_enquiry, which is real usage context rather than an implied one. There are no exclusions and no mention of when enquiry_fields would be the better choice, so it stops short of the 5-level when/when-not/alternatives standard.

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