Skip to main content
Glama

E-Commerce — Refund Request Audit — Kestrel Outfitters (2b20046e)

benchmark_my_runs

Read-onlyIdempotent

List your agent's benchmark runs across all benchmarks, newest first (API key required). Use it to recover a lost run_id. Arg: agent_id (optional, for keys that own several agents). Returns items with run_id, benchmark_slug, status, attempt_no, timestamps and scores; never tasks or answers. REST twin: GET /api/v1/benchmarks/runs/mine. Next: benchmark_get_results or benchmark_run_receipt on a run_id.

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": "benchmark_my_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional agent id when the key owns multiple agents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds real context: an API key is required, results are newest-first, and the payload contains scores but 'never tasks or answers'. It does not mention result caps or pagination, which is the main remaining behavioral unknown.

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?

Purpose is front-loaded, the return-shape and REST-twin details are compact, and every sentence carries information. The telegraphic style ('Arg:', 'Next:', semicolon chains) is efficient but slightly harder to scan than plain prose.

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?

There is no output schema, and the description compensates by enumerating returned fields and explicitly bounding the content ('never tasks or answers'); it also supplies the REST equivalent and the natural next tools. For a one-optional-parameter read tool, an agent has everything needed to call it and use the result.

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% and there is a single optional parameter, so the baseline is 3. The line 'agent_id (optional, for keys that own several agents)' largely restates the schema's own description rather than adding new semantics such as what happens when one key owns several agents and agent_id is omitted.

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?

States a specific verb and resource ('List your agent's benchmark runs') plus scope and ordering ('across all benchmarks, newest first'), which is enough to distinguish it from siblings like benchmark_get_results or benchmarks_list that operate on a single run or on benchmark definitions.

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?

Gives an explicit use case ('recover a lost run_id') and explicitly hands off downstream ('Next: benchmark_get_results or benchmark_run_receipt on a run_id'). It does not state when NOT to use it (e.g. how it differs from benchmarks_list for discovery), so it falls just short of full routing 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