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 Digital marketing agency Swindon: it starts an enquiry with Digital marketing agency Swindon, 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.6/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 meaningful work: it clarifies that nothing is bought, ordered or paid, that no quote is guaranteed, and that the process is free — exactly the disambiguation an agent needs to avoid treating an enquiry as a transaction. It also previews the return content (recipient of details, consent wording, confirmation method). It stops short of stating whether it is strictly read-only or whether any record is created on call.

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?

"Read first" is front-loaded and the disclaimers are short and purposeful, but the full brand string "Digital marketing agency Swindon" appears twice within a single sentence, which is wasteful. The statement "Nothing is bought, ordered or paid... it is free" is slightly redundant but earns its place as behavioral clarification.

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-annotation, no-output-schema tool, the description covers the essentials: what it returns and the key non-transactional guarantees. Missing is any distinction from enquiry_fields and any note on whether calling it has side effects, both minor for a descriptive tool.

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 input schema declares zero parameters, so there is nothing for the description to disambiguate; the baseline is 4.

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

Purpose3/5

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

The description frames itself almost entirely as an explanation of submit_enquiry ("States plainly what submit_enquiry does") rather than stating its own action, though "Read first" and "Also returns..." do signal that this is an informational read tool returning consent wording and recipient details. An agent can infer the purpose, but the framing risks conflating the describer with the submitting tool, and it never differentiates itself from the sibling enquiry_fields.

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

Usage Guidelines3/5

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

"Read first" gives a clear ordering cue relative to submit_enquiry, implying this should be consulted before submitting. There is no explicit when-not guidance and no mention of enquiry_fields, so the agent gets only implied routing between the two read-oriented siblings.

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