door_acff25cbe9fb

quote

Get a quote for one action call. The quote pins the exact tool + args and returns a quote_id for confirm. Nothing executes until confirm. Quotes expire after 10 minutes.

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": {
      "tool": "<tool>"
    },
    "name": "quote"
  }
}

Input Schema

Name	Required	Description
`args`	No	Arguments for the action, matching its parameters schema (max 16KB).
`tool`	Yes	An action name from list_actions.
`agent_key`	No	Optional agent key, minted by a user account on this platform. Don't hunt for one first: quote without a key and, if the action needs one, the quote returns a phone connect link for your human — your key is minted and delivered automatically through the same quote.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds that nothing executes until confirm (no side effects), that quotes expire after 10 minutes, and that the quote pins the exact tool + args. These are meaningful behavioral facts beyond what the schema provides.

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?

Three short sentences, each earning its place: purpose, behavior, and expiry. It is front-loaded with the main action and contains no filler or redundancy.

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

Completeness3/5

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

For a 3-parameter tool with no output schema and no annotations, the description covers the workflow, non-execution, and expiry, but it omits the quote's key content—there is no mention of the cost/price/currency or the response shape beyond a quote_id. This leaves an agent uncertain what the actual quote will contain.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description indirectly reinforces the 'tool' and 'args' parameters by saying the quote pins the exact tool + args, but it adds no per-parameter detail beyond the already-complete schema descriptions.

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

Purpose5/5

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

Clearly states 'Get a quote for one action call' with a specific verb and resource. It differentiates from the sibling 'confirm' by explaining that the quote returns a quote_id for confirm, so an agent knows this is the pricing/preview step, not the execution step.

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 description gives an explicit usage condition: use quote to pin tool + args and get a quote_id before confirm. 'Nothing executes until confirm' tells the agent when not to rely on quote for execution. However, it doesn't explicitly discuss alternatives like list_actions or include a dedicated when-not-to-use section, so it stops short of a full 5.

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

All door_acff25cbe9fb tools Inspect

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

Need Help?