Skip to main content
Glama

E-Commerce — Return Review — Kestrel Outfitters (fb3b8adc)

benchmark_get_results

Read-onlyIdempotent

Read status and score breakdown for one of YOUR runs (API key required). A missing principal or a run you do not own cannot leak another agent's score or gold. task_view="stubs" re-lists this attempt's task sizes without the prompts (resume a run by run_id). REST twin: GET /api/v1/benchmarks/runs/{run_id}.

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": {
      "run_id": "<run_id>"
    },
    "name": "benchmark_get_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesUUID of a run from benchmark_start_run.
agent_idNoOptional agent id when the key owns multiple agents.
task_viewNofull (default): every task with its prompt. stubs: tasks is [] and task_stubs lists {ordinal, visibility, grader_type, prompt_chars}; fetch each prompt with benchmark_get_task {run_id, ordinal}.full

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Identify one of the caller's benchmark runs."New value: +"``benchmark_get_results``: one run plus the opt-in stub view."
    • addedInput schema / properties / task_view
      Added value: +{
      +  "default": "full",
      +  "description": "full (default): every task with its prompt. stubs: tasks is [] and task_stubs lists {ordinal, visibility, grader_type, prompt_chars}; fetch each prompt with benchmark_get_task {run_id, ordinal}.",
      +  "enum": [
      +    "full",
      +    "stubs"
      +  ],
      +  "title": "Task View",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds value beyond them by disclosing the API-key requirement and the ownership enforcement rule ('a run you do not own cannot leak another agent's score or gold'), which is real behavioral context. It does not describe the shape of the returned breakdown, which is a modest gap.

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?

Three tight sentences, front-loaded with what is returned and immediately followed by the access constraint and the stubs option. The REST twin note is compact and useful; only the stubs clause mildly duplicates the schema.

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 does the needed work by naming the returned content (status and score breakdown) and covering auth and ownership. A short note on the structure of the breakdown or what happens for a run still in progress would make it complete.

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 run_id, agent_id, and task_view are already well documented in the schema, and the description adds little beyond restating the stubs behavior. The one extra is the resume-a-run use case, but the mechanics of task_view are already in the parameter description.

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 gives a specific verb and resource ('read status and score breakdown') plus a clear scope ('one of YOUR runs'), which separates it from the listing tools like benchmark_my_runs or benchmarks_list. It stops short of naming a sibling tool outright, so differentiation is inferred from scope rather than stated.

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 establishes the context of use (fetch results for an owned run) and gives concrete guidance for the task_view='stubs' path, including that it enables resuming a run by run_id. There is no explicit 'do not use this when…' statement or named alternative, which keeps it below a 5.

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