Skip to main content
Glama

LLMBenchmark.ai MCP Server: LLM Benchmarks and API Prices

recommend_model

Which model should I use for this task? Maps the task text to a category (coding, agentic, reasoning, math, knowledge, web design, or overall when nothing matches) by a fixed keyword map, filters by output price per million tokens, context length and open weights, and ranks by that category's benchmark board. Deterministic, no LLM call. Returns top_k models with scores, rank, prices, context, page URLs and a one-line reason. overall is the LLMBenchmark Index: a weighted mean of the Vibe Coding Index, the agentic, reasoning, math and knowledge indexes, the Artificial Analysis Intelligence Index and the LMArena text Elo, with a 90% margin.

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": {
      "task": "<task>"
    },
    "name": "recommend_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
top_kNo
open_weights_onlyNo
min_context_tokensNo
max_output_price_per_mNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it declares the tool is deterministic with no LLM call, explains the fixed keyword-map categorization, the filter dimensions, the ranking source, and exactly what the response contains (scores, rank, prices, context, page URLs, one-line reason). It even defines how the 'overall' index is composed and its 90% margin, which is behavior an agent could not infer elsewhere.

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 question front-loads intent and the pipeline is described in one dense but readable sentence. The closing sentence detailing the weighted composition of the 'overall' index is long and only relevant to one category, so it is the one part that does not fully earn its space.

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 payload, and it covers the categorization, filtering, and ranking logic for a five-parameter tool with zero schema documentation. 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 description coverage is 0%, so the description must compensate, and it does: task text, top_k ('returns top_k models'), open weights, context length, and output price per million tokens are all named with their role in the pipeline. It stops short of stating defaults or edge-case behavior (e.g. what happens when filters exclude everything), which keeps it from a 5.

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 opens with the exact user question it answers and then states the concrete mechanism: map task text to a category via a fixed keyword map, filter by price/context/open weights, rank by that category's benchmark board. This is a specific verb+resource that an agent can distinguish from siblings like get_leaderboard or compare_models without opening any schema.

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 clear context for when to call it (a task description needs a model recommendation) and an explicit fallback rule: 'overall when nothing matches'. It does not, however, state when to prefer a sibling such as compare_models or get_prices instead, so the routing guidance is strong but not complete.

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.