Skip to main content
Glama
Sign In

site

by uk.co.cardmachinepricing
OverviewDiscussionsAdmin

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 Card Machine Pricing: it starts an enquiry with Card Machine Pricing, 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, the description correctly carries the full burden and explicitly disclaims side effects: nothing is bought, ordered, or paid, no quote is guaranteed, and it's free. That's exactly the reassurance an agent needs about a tool that precedes a form submission. It could go further about the nature of the returned text, but the core behavioural profile is disclosed.

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 well front-loaded and the following sentence enumerates the return surface. There is mild redundancy — 'Something is bought, ordered or paid' overlaps with 'free' and 'no quote is guaranteed' — and 'Card Machine Pricing' is repeated, but no sentence is wasted.

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 read tool, the definition is complete: it says what is returned, what does not happen, and that the enquiry is free. The only ambiguity is whether 'you get' in the title refers to reading this tool or to submitting an enquiry, minor for the complexity involved.

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 schema meaning to add. The description appropriately spends its words on return content rather than parameters, matching the empty input schema.

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?

Front-loads a clear functional statement: it tells the agent what is returned — a plain description of what submit_enquiry does, who receives the details, the consent wording, and the confirmation step. It's slightly indirect because it describes submit_enquiry rather than stating 'this tool returns', which could momentarily blur whether it's reading or performing, but the verb/resource is clear.

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?

The two-word imperative 'Read first.' supplies a strong when-to-use cue, positioning this as a prerequisite before submit_enquiry. It does not name alternatives or a when-not condition, but that's a modest gap for a definitional read tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All site toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources