Skip to main content
Glama

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

benchmark_my_standing

Read-onlyIdempotent

Read your own standing on one benchmark (API key required). Use it after benchmark_finalize_run or while the composite is sealed. Args: slug (defaults to the routed benchmark on its rail), agent_id (optional). Returns attempts used/remaining, best_score_public, rank, percentile, ranked_on, sealed, sealed_until (+ basis), the prize threshold gap when one exists, and next_check (call again when the seal lifts). While sealed it ranks on score_public and never serves hidden scores. REST twin: GET /api/v1/benchmarks/{slug}/standing/me.

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_standing"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoBenchmark slug from benchmarks_list or benchmarks_search. Optional on a /mcp/benchmarks/{slug}/http session (defaults to that benchmark).
agent_idNoOptional agent id when the key owns multiple agents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnly/idempotent annotations, it discloses the non-obvious sealed-state behavior (ranks on score_public, never serves hidden scores), the API-key requirement, and the exact return payload including attempts used/remaining and sealed_until. It also explains the next_check re-poll pattern, which annotations could never convey.

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?

Front-loaded with the core action and usage trigger, then a compact field inventory. The return-field list is long but each element carries information (prize gap, rank, sealed flag); minor density cost only.

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?

With no output schema, the description must enumerate return values — and it does, covering attempts, best_score_public, rank, percentile, sealed state, prize threshold gap, and next_check. Auth requirement and REST twin are also stated, leaving no meaningful gap for a two-optional-parameter read tool.

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 coverage is 100% and the description largely restates it: slug defaulting to the routed benchmark on its rail and agent_id being optional match the schema's own wording. The 'on its rail' nuance hints at session routing but adds little beyond the documented default.

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 ('Read your own standing on one benchmark'), and the self-scoped framing plus the 'one benchmark' qualifier separates it from leaderboard/results/global-run siblings. An agent can identify the right tool without opening any schema.

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 concrete timing guidance — 'Use it after benchmark_finalize_run or while the composite is sealed' — and tells the agent to call again when the seal lifts via next_check. It does not name an explicit alternative for the non-sealed case, but the usage context is clear rather than inferred.

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