Skip to main content
Glama

The Aggregate — LLM benchmark aggregate

by ai.theaggregate
OverviewDiscussionsAdmin

Search models

search_models
Read-onlyIdempotent

Find ranked models by (partial) name or provider. Returns rank, Aggregate Rating and the model page URL. One row per model by default, fused across reasoning-effort settings.

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-25, default 10).
queryYesModel or provider name fragment, e.g. "opus" or "deepseek".
include_variantsNoReturn each reasoning-effort variant separately (e.g. "Claude Opus 4.6 (High)") instead of one fused row per model. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_variants
      Added value: +{
+  "description": "Return each reasoning-effort variant separately (e.g. \"Claude Opus 4.6 (High)\") instead of one fused row per model. Default false.",
+  "type": "boolean"
+}
  2. 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 this a safe read (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds real behavioral context beyond them: the returned fields (rank, Aggregate Rating, page URL) and the default de-duplication/fusion across reasoning-effort settings, which explains why a caller may see fewer rows than expected.

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?

Three short sentences, front-loaded with the capability and followed by return shape and the default row behavior. Nothing is repetitive or decorative; every sentence carries 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?

With no output schema, the description correctly takes on the return-value burden by naming the returned fields and the one-row-per-model default. It stops short of covering result ordering/pagination specifics, though limit is already documented in the schema.

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 description coverage is 100%, so the schema already documents query, limit and include_variants. The description reinforces the variant-fusion semantics of include_variants and the partial-match nature of query, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource plus the matching key (partial name or provider), so the agent knows exactly what comes back: ranked models. It does not name or distinguish itself from siblings like get_model or compare_models, which is the only thing keeping 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?

Usage is implied by the description (search when you have a name/provider fragment), but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as get_model for an exact single-model lookup. Minimum viable guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Aggregate — LLM benchmark aggregate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources