Skip to main content
Glama

Cheap First

Ask Cheap First

ask_cheap_first

Answer a question the Cheap First way: Dolphin answers, SERV Reasoning scores it, and a premium model answers instead only if the score misses the pass mark. Returns the answer, whether it escalated, the check score, the cost and the estimated saving. Free calls use the public demo limits (600 characters, 10 an hour per IP, 300 a day). Send Authorization: Bearer cf_... or an x402 payment of $0.005 USDC on Base for the paid limits (2000 characters). To receive the x402 challenge, send the header X-Cheap-First-Paid: 1. mode: strict escalates more often (pass mark 85), balanced is the default (75), budget escalates less often (60).

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": {
      "question": "<question>"
    },
    "name": "ask_cheap_first"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNostrict, balanced (default) or budget. Unknown values are treated as balanced.
questionYesThe question. 600 characters on the free demo, 2000 when paid.

Output Schema

NameRequiredDescriptionDefault
modeNo
tierNo
modelNoLabel of the model that produced the answer.
answerYesThe answer to give the user.
costUsdYesWhat Cheap First spent on this call, in US dollars.
paidUsdNoWhat the caller paid, on the paid tier.
savedUsdYesEstimated saving against sending the question to the premium model alone. Can be negative when an escalation cost more than that.
escalatedYesTrue when the check failed and the premium model answered instead.
answeredByNocheap is Dolphin. premium is the frontier model.
checkScoreYesThe checker's score for the cheap answer, from 0 to 100.
checkReasonNoThe checker's one-line reason.
creditsLeftNoPrepaid answers left on the key, when one was used.
transactionNox402 settlement transaction, when there is one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses hard rate limits (600 chars, 10/hour, 300/day per IP), the paid tier ceiling (2000 chars), the exact payment mechanism ($0.005 USDC on Base via x402 or a Bearer cf_ key), and what escalation costs. These are the operational facts an agent needs before invoking a metered external call.

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?

The first sentence front-loads what the tool does and what it returns, then moves to limits, payment, and mode tuning in a logical order. It is dense with parenthetical constraints and runs slightly long, but no sentence is filler.

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

Completeness5/5

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

An output schema exists, yet the description still summarizes the return shape, and it fully covers auth paths, tier limits, escalation logic, and mode tuning for a two-parameter tool with a paid external call. Nothing an agent needs in order to call this correctly is missing.

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?

Schema coverage is 100%, so the enum values and the question length constraint are already documented. The description still adds real meaning by attaching numeric pass marks (85/75/60) to each mode, which the schema does not carry, telling the agent what each mode actually changes.

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?

The description states a specific verb and resource and spells out the actual pipeline: Dolphin answers, SERV Reasoning scores, a premium model escalates only on a failed pass mark. It also enumerates the return payload (answer, escalation flag, score, cost, saving), which distinguishes it clearly from the sibling stats tool.

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?

It gives concrete conditions for each mode — strict escalates more (pass mark 85), balanced default (75), budget less (60) — and explains exactly how to move from free demo to paid limits, including the X-Cheap-First-Paid header needed to trigger the x402 challenge. It does not say when an agent should skip this tool entirely, but the operating context is otherwise clear.

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.