Skip to main content
Glama

Request a quote

request_quote

Send a countertop quote request to the ATX Granite King crew. Only call this when the user explicitly asks to be contacted and has given their own phone or email.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
nameYes
sqftNo
emailNo
phoneNo
stoneNo
detailsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent but non-destructive call; the description usefully adds that the request goes to a human crew and requires user consent plus their own contact info. It does not say what happens after submission (callback timing, whether duplicate submissions create duplicate requests, or what is returned for a tool with no output schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences; the action is front-loaded and the gating condition follows immediately. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter outbound submission tool with no output schema and no annotation detail about outcomes, the description covers only the consent gate. An agent still lacks any guidance on what the remaining fields mean or what to expect after the request is sent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description must carry the burden and largely does not. It does add one meaningful constraint not enforced by the schema, that a phone or email must be supplied and must be the user's own, but city, sqft, stone, and details are left entirely unexplained.

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?

States a concrete verb and resource: send a countertop quote request to a named business. It is distinguishable from quote-retrieval siblings like get_quote, though it does not explicitly contrast with generate_quote, which an agent could plausibly confuse it with.

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?

Gives an explicit precondition for calling: only when the user explicitly asks to be contacted and has supplied their own phone or email. That is strong when-to-use guidance with an exclusion condition, but it never names the alternative tools (e.g. generate_quote or estimate_job) an agent should use when the user just wants a number.

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