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 Tools for PPC: it starts an enquiry with Tools for PPC, 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?

With no annotations supplied, the description carries the full disclosure burden and does it well: nothing is bought, ordered or paid, no quote is guaranteed, it is free, and the team reads and replies directly. This is exactly the kind of consequence-framing an agent needs before routing a user here. It never states outright that the call is side-effect free and read-only, leaving that to be inferred from 'Read first' and 'States plainly'.

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?

Two sentences, front-loaded with the actionable instruction and then the payload. The clause 'with Tools for PPC, whose team reads it and replies directly' plus the leading 'it starts an enquiry with Tools for PPC' repeat the same idea, which is the only real waste.

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 tool with no output schema, the description must say what comes back, and it does: recipient details, consent wording, and the confirmation mechanism. Nothing about invocation is missing. A brief note that the content is static documentation rather than live account data would close the last gap.

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 and the description does not invent any, so there is no parameter semantics to add. Baseline for a zero-parameter tool applies.

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 concrete verb and the exact content returned: what submit_enquiry does, who receives the details, the consent wording, and how confirmation happens. It also implicitly distinguishes itself from submit_enquiry by being the read-first explainer. It stops short of the crispest possible framing ('returns static documentation about the enquiry flow, performs no action') and refers to itself in the third person, which costs a little clarity.

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 sequencing instruction that tells the agent to call this before submit_enquiry. What is missing is any exclusion or fallback guidance, e.g. when to call enquiry_fields instead, or what to do if the agent has already read this once. The usage context is clear but the alternatives are not addressed.

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