Skip to main content
Glama

Cheap First

Cheap First benchmark

cheap_first_stats
Read-onlyIdempotent

Published benchmark figures. The main run is 143 questions: what Cheap First spent, what the premium model alone would have cost, how many Dolphin answered, and the average quality scores. Also includes the harder 97-question run. Does not call a model.

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": "cheap_first_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
benchmarkYesThe main benchmark, with costs rounded to cents the way the site quotes them, plus exactUsd.
resultsPageYes
hardBenchmarkYesThe harder benchmark graded by code, or null if it was not built.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely new context: the figures are static/published and no model is invoked, which tells the agent there is no inference cost or latency and that the data is fixed rather than computed per request.

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 lead sentence establishes the resource immediately, and the following sentences add the run sizes and metric list without filler. The enumeration of metrics is slightly list-heavy but every item is informative rather than padding.

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?

With an output schema present, the description does not need to enumerate return values, yet it does so anyway, which is mildly redundant but harmless. For a zero-parameter, static-data tool the definition is complete enough for an agent to call it correctly; only explicit routing guidance versus the sibling 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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline of 4 applies. The description correctly avoids inventing inputs and simply describes what the parameterless call yields.

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?

The description states the resource concretely (published benchmark figures) and enumerates the specific metrics returned for a named 143-question run plus a 97-question run, so an agent knows exactly what data comes back. It lacks an explicit verb like 'Returns' but the content list leaves no ambiguity about what the tool does.

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?

Usage is only implied: 'Does not call a model' hints this is the no-cost way to obtain the numbers, implicitly contrasted with ask_cheap_first. There is no explicit when-to-use statement, no named alternative, and no condition telling the agent to prefer this over asking the model.

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.