Skip to main content
Glama

LLMBenchmark.ai MCP Server: LLM Benchmarks and API Prices

compare_models

Two models side by side: score on every category board where both were measured, prices, context. Names are matched loosely: 'claude opus', 'gpt-5' or a slug all work.

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_a": "<model_a>",
      "model_b": "<model_b>"
    },
    "name": "compare_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_aYes
model_bYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose two useful behaviors: only categories where both models were measured are scored, and name lookup is fuzzy. It says nothing about unresolved or ambiguous model names, or about failure behavior, leaving the main operational risk undisclosed.

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?

Two sentences with zero filler; the comparison scope and returned fields come first, and the input-matching caveat follows. Nothing is repeated from the schema or title.

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 the return shape needn't be explained, and the description covers both inputs and the comparison scope. The remaining gap is edge-case behavior for unmatched or ambiguous model names on a tool that requires both parameters.

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: both parameters are documented as accepting loose display names or slugs, with 'claude opus' and 'gpt-5' as concrete examples. It stops short of stating precedence when a loose match is ambiguous or whether model_a and model_b are ordered in the output.

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?

"Two models side by side" plus an enumeration of what comes back (per-category board scores where both were measured, prices, context) gives a specific verb-and-resource picture that separates it from single-model get_model or get_prices. It never names a sibling explicitly, so the differentiation is inferred from scope rather than stated.

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 pairwise scope implies when to reach for this over get_leaderboard or get_model, but no when-not condition or alternative is spelled out. The note on loose name matching is a usage aid, though it addresses input format rather than tool selection.

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.