Skip to main content
Glama

LLMBenchmark.ai MCP Server: LLM Benchmarks and API Prices

get_prices

API prices (USD per million tokens), cheapest output price first: the maker's own price when it serves the model on OpenRouter, else the median of providers (price_basis says which), plus the cheapest provider. Filter by model name and/or maker; limit is 1 to 100.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
makerNo
modelNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses ordering (cheapest output first), the price-selection rule (maker's own price if served on OpenRouter, else provider median, indicated by price_basis), and that the cheapest provider is included. It omits auth/permission requirements and pagination behavior, so not a 5.

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?

One dense sentence, front-loaded with the resource and units, followed by output semantics and then input constraints — a logical order. The mid-sentence parenthetical about price basis is heavy but each clause adds real information.

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?

An output schema exists, so return values needn't be enumerated, and the description still explains the price_basis field and the included cheapest-provider entry. For a 3-param, zero-required tool this is sufficient, with only match semantics for the filters left open.

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 0%, so the description must compensate, and it does for all three parameters: model and maker are named as filters, and limit gains a constraint (1 to 100) the schema lacks. It does not clarify whether model/maker matching is exact or substring, leaving some ambiguity.

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?

Specific verb+resource: it returns API prices in USD per million tokens, with an explicit sort order (cheapest output first). The pricing-basis rule (maker price vs. provider median) is unambiguous. It does not differentiate itself from siblings like compare_models or get_model, which keeps it from a 5.

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?

It says how to narrow results ('Filter by model name and/or maker') and bounds the limit (1 to 100), which implicitly tells the agent this is a filtered price lookup. However, it never states when to prefer this over compare_models or get_model, and no exclusions or prerequisites are given.

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.