Skip to main content
Glama

Wall of Decks

section_benchmarks

Benchmarks across decks: median slide count, and for each section the share of decks that have it and the slide where it usually first appears.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "section_benchmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the shape of the results (median slide count, share of decks per section, typical first slide), but says nothing about whether this is a read-only aggregation, how expensive it is to compute across all decks, or whether results are filtered by anything by default.

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?

One dense sentence with no filler, and the headline metric (median slide count) is front-loaded. The trailing clause about first-appearance slide is slightly convoluted but still clear.

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

Completeness3/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 does a reasonable job describing return values, which is the main thing an agent needs. However, for a single-parameter tool it leaves the only parameter unexplained, which is a real completeness gap given 0% schema coverage.

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 single 'stage' parameter (enum: early, seed) is entirely undocumented in structured data. The description never mentions 'stage' at all, leaving the agent to guess whether it filters the benchmark population or is required.

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 resource and computation: 'Benchmarks across decks: median slide count' plus per-section prevalence and typical first-appearance slide. This is clearly an aggregate/analytics tool, which distinguishes it implicitly from retrieval siblings like get_deck, list_decks, and search_slides.

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?

The description never says when to reach for this tool versus the sibling list/search tools, nor any precondition or exclusion. An agent can infer it is for statistics rather than raw content, but this is inference, not guidance.

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