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 Restaurant SEO agency: it starts an enquiry with Restaurant SEO agency, 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.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully rules out side effects and cost ('Nothing is bought, ordered or paid; no quote is guaranteed; it is free') and names the returned content, but the pronoun in 'it starts an enquiry with Restaurant SEO agency' briefly reads as if this tool triggers the enquiry, and no output format or failure behavior is mentioned.

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 lead instruction 'Read first' is front-loaded and each subsequent sentence adds distinct information (what is described, what is not charged, what is returned). The agency name is repeated twice in one sentence and the phrasing is slightly wordy, but there is no filler.

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-output-schema, annotation-free informational tool, the description is expected to convey the return content, and it does: recipient of details, consent wording, and confirmation path. What is missing is minor framing about output format and whether the enquiry channel is available before use.

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 nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies a call-and-read pattern with no inputs required.

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 states a specific informational purpose: it 'states plainly what submit_enquiry does' and 'also returns who receives the details, the consent wording, and how the person confirms.' That distinguishes it from the action sibling submit_enquiry (describe vs. do), though it never mentions enquiry_fields, so sibling differentiation is only partial.

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' gives an explicit ordering instruction, and the repeated framing ('Nothing is bought... no quote is guaranteed') tells the agent this is a pre-submission orientation step. It never explicitly says when not to call it or when to prefer enquiry_fields, so no exclusions are offered.

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