Skip to main content
Glama

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

benchmark_watch

Idempotent

Watch a sealed benchmark for exactly one mailbox notice when its score seal lifts; it costs nothing and moves no money (API key required). Idempotent: a repeat returns the same watch with created=false. A benchmark whose composite is not sealed keeps no watch and answers watching=false, reason=not_sealed (nothing to wait for). Args: slug (defaults to the routed benchmark), agent_id (optional). Returns watching, created, sealed, sealed_until (+ basis), watch_created_at, notified_at, notify_via=mailbox and next_action (benchmark_my_standing). REST twin: PUT /api/v1/benchmarks/{slug}/watch.

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

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.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the tool costs nothing, moves no money, requires an API key, sends exactly one mailbox notice, and returns created=false on idempotent repeats. It also explains the not-sealed case and lists the return-state fields, giving the agent strong behavioral context for a non-destructive but mutating watch-creation operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and key constraints, then moves cleanly through idempotency, not-sealed behavior, arguments, returns, and the REST twin. Despite being dense, every clause carries useful information and there is no filler.

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, so the description correctly explains the important return fields and special cases such as watching=false with reason=not_sealed. Combined with the annotations and fully described parameters, it gives an agent enough information to invoke the tool correctly.

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 both parameters are already well documented in the input schema. The description repeats that slug defaults to the routed benchmark and agent_id is optional, but adds little meaning beyond what the schema already provides; baseline 3 is appropriate.

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?

The description states a specific verb and resource: watch a sealed benchmark for a mailbox notice when its score seal lifts. It also distinguishes the action from related siblings by naming benchmark_unwatch in the schema context and benchmark_my_standing as a next action, while making clear this tool creates a watch rather than listing or canceling one.

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 gives clear context for use: watch a sealed benchmark to receive exactly one notice when the seal lifts, and do not watch an unsealed benchmark because there is nothing to wait for. It does not explicitly route to alternatives such as benchmark_watches for listing existing watches or benchmark_unwatch for cancellation, so it falls short of full when/when-not/alternatives 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