Skip to main content
Glama

capability_priors

Outside evaluations for one capability across base models (each says what it measured). No ranking.

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": {
      "capability": "<capability>"
    },
    "name": "capability_priors"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNo
capabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral context — results are self-describing ('each says what it measured') and unordered ('No ranking') — but says nothing about what happens for an unknown capability, whether availability varies by layer, or the response envelope.

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 no filler, and the core subject ('Outside evaluations for one capability across base models') is front-loaded. The parenthetical and the 'No ranking' disclaimer each earn their place, though the result is arguably clipped to the point where required meaning is missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and 2 parameters at 0% schema coverage, the description should carry the load but does not: the capability vocabulary and the meaning of the layer enum are completely unaddressed. An agent could call it, but not confidently or correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 explain both parameters and does not. 'One capability' hints that capability is a single free-text value, but the accepted vocabulary and maxLength are undocumented; the layer enum (provider/independent/human) is never addressed, even though 'Outside evaluations' only loosely hints at it.

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 states specifically what the tool returns: outside (third-party) evaluations for a single capability, aggregated across base models. It also clarifies the shape of the result ('each says what it measured') and that it is not a ranking. It does not name the closely related sibling model_priors, so the distinction from that tool must be inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'No ranking' implicitly steers an agent elsewhere if it wants ordered/leaderboard output, but no alternative is named and no when-to-use condition is given. Nothing tells the agent when to prefer capability_priors over model_priors or explore_performance.

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.

Resources