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 EPOS system for retail: it starts an enquiry with EPOS system for retail, 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.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the substantive semantics (nothing is bought, ordered or paid; no quote guaranteed; free) and what the response contains (who receives the details, consent wording, how the person confirms). It does not explicitly say the call itself is side-effect-free/read-only, which is the main remaining gap.

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?

'Read first' is well front-loaded, but the text repeats itself: 'States plainly what submit_enquiry does on EPOS system for retail: it starts an enquiry with EPOS system for retail...' restates the same product qualifier twice. Tightening that redundancy would improve the scan.

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 informational tool, the description covers what the call returns and the commercial framing an agent needs. A brief note that it is a safe read-only lookup would make it fully complete.

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 to disambiguate; the baseline for a 0-parameter tool applies. The description correctly adds no parameter noise and focuses on what the call yields.

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 intent: it plainly describes what submit_enquiry does (starts an enquiry, a human team reads and replies) and what it returns (recipient of details, consent wording, confirmation step). It is distinguishable from submit_enquiry itself, though the phrasing 'States plainly what submit_enquiry does' momentarily blurs whether this tool performs the enquiry or explains it, and relies on the title to disambiguate.

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' implies ordering relative to submit_enquiry, giving implied usage guidance. However, no explicit when-to-use/when-not-to-use rule or named alternative is provided beyond that hint, leaving the agent to infer that this is a preamble to submit_enquiry.

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