Phase Router

quote

Read-only

Get the price ceiling for a chat request without paying (the gateway's 402 quote).

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

Input Schema

Name	Required	Description
`model`	Yes	model id from list_models, or a class: auto \| eco \| premium \| agentic
`prompt`	No	single user message (use messages for multi-turn)
`system`	No	optional system prompt
`session`	No	saved session id (from the session tool or a /s/<id> link): the gateway prepends its history and appends this turn
`messages`	No	full conversation; overrides prompt/system
`max_tokens`	No	output cap; also bounds the price ceiling
`temperature`	No	sampling temperature 0–2 (Claude ignores it)

Output Schema

Name	Required	Description
`free`	Yes
`model`	Yes
`network`	Yes
`ceiling_usd`	Yes
`paid_by_key`	No	true when a Phase API key pays: its balance and daily cap apply, max_usd_per_call does not
`per_call_usd`	Yes
`wallet_can_pay`	Yes
`input_usd_per_1m`	Yes
`max_usd_per_call`	No	largest quote the wallet will sign (wallet mode only)
`output_usd_per_1m`	Yes
`input_tokens_estimate`	Yes
`max_output_tokens_priced`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that this is a no-charge quoting operation mirroring the 402 response, which is genuinely useful context, but says nothing about whether pricing varies by provider or how stale a quote may be.

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?

A single compact sentence with the operation front-loaded and the parenthetical explaining the 402 reference. No filler, though the parenthetical is somewhat inside-baseball.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. However, for a quoting tool the description never mentions that max_tokens bounds the ceiling, nor how it relates to the 'chat', 'usage' or 'receipt' siblings, leaving notable gaps.

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% and every parameter is documented in the schema, including the prompt/messages/session override relationships, so the description need add little. It contributes no parameter meaning of its own beyond the general notion of a quote, fitting the baseline.

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?

Names a specific verb and resource ('Get the price ceiling for a chat request') and adds a useful gloss ('the gateway's 402 quote'). It distinguishes itself from the sibling 'chat' by the 'without paying' clause, though it doesn't explicitly route to 'receipt' or 'usage'.

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?

The phrase 'without paying' implies when to use it (pre-flight cost check before calling chat), but no explicit when-not or named alternative is given. Usage is inferable rather than stated.

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

All Phase Router 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?