Skip to main content
Glama

LLMBenchmark.ai MCP Server: LLM Benchmarks and API Prices

get_model

One model: maker, release date, prices, context, open weights, and its score and rank on every category board. Name or slug.

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

Input Schema

NameRequiredDescriptionDefault
modelYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it does disclose what the response contains (all profile fields plus per-category scores and ranks). It says nothing about behavior on an unknown model (error vs. empty), whether lookup is exact-match, or any auth/rate constraints, which are real gaps for a lookup tool.

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?

Two short sentences with the resource and its contents front-loaded; nothing is filler. The telegraphic fragment style ('One model: ...') omits an explicit verb, but the content is dense and readable.

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-value detail is already covered, and with one simple string parameter the definition needs little more. The main missing element is failure behavior for a non-matching model identifier, which is minor for a read-only lookup.

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 0% for the single 'model' parameter, so the description must compensate. It adds genuine meaning by stating the parameter accepts either a name or a slug, but gives no format, casing, or ambiguity-resolution detail for that choice.

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 identifies a single-resource retrieval ("One model") and enumerates the resource's contents (maker, release date, prices, context, open weights, score/rank per category board), which is enough to distinguish it from compare_models and get_leaderboard. The verb is only implied by the field list rather than stated, keeping it short of 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?

There is no explicit when-to-use or when-not-to-use statement. Usage is only implied by the field enumeration: this is the tool for full detail on one specific model, which implicitly contrasts with the leaderboard/comparison siblings, but nothing tells the agent when to prefer get_prices or compare_models instead.

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.