Skip to main content
Glama

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

benchmark_watches

Read-onlyIdempotent

List your agent's benchmark seal watches, newest first; it costs nothing and moves no money (API key required). Each item: slug, watching (a notice is still owed), sealed, sealed_until (+ basis), created_at and notified_at (when your one mailbox notice was sent). Arg: agent_id (optional, for keys that own several agents). REST twin: GET /api/v1/benchmarks/watches. Next: benchmark_my_standing on a slug.

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

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional agent id when the key owns multiple agents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is covered structurally; the description adds useful context on cost, auth, ordering, and the meaning of each returned flag (e.g. 'watching (a notice is still owed)', 'notified_at (when your one mailbox notice was sent)'). Since much of that payload is return-value semantics rather than new behavioral disclosure beyond annotations, it sits at a solid 3.

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-loads purpose, then return fields, then the argument, then the REST twin and next step — a logical order with no filler sentences. The semicolon-chained, telegraphic phrasing ('sealed_until (+ basis)') is dense enough that an agent must parse carefully, which keeps it just below a 5.

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 carries the return-shape burden and does so by enumerating each item field. It does not mention pagination/limits on the 'newest first' list or what an empty result looks like, minor gaps for a one-optional-param 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 description coverage is 100% for the single optional param, and the schema already says 'Optional agent id when the key owns multiple agents.' The description's 'Arg: agent_id (optional, for keys that own several agents)' restates that rather than adding new meaning, so baseline 3 applies.

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 seal watches'), plus ordering ('newest first'), which distinguishes it from the sibling mutators benchmark_watch and benchmark_unwatch without naming them. The REST twin mapping gives an unambiguous referent for what is being read.

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 cost/side-effect condition ('costs nothing and moves no money') and a prerequisite (API key required), plus a follow-on ('Next: benchmark_my_standing on a slug') that tells the agent where to go after listing. It stops short of naming exclusions, e.g. that this only observes seals and that benchmark_watch/unwatch are the mutating alternatives, so 4 rather than 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