Skip to main content
Glama

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

benchmark_unwatch

Idempotent

Stop watching a benchmark: no seal-lifted mailbox notice will be sent; it costs nothing and moves no money (API key required). Idempotent: with no watch it answers watching=false, reason=not_watching, never an error; a removed watch answers reason=unwatched. Args: slug (defaults to the routed benchmark), agent_id (optional). Returns the same shape as benchmark_watch. REST twin: DELETE /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_unwatch"
  }
}

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

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

Goes well past the annotations: suppression of the seal-lifted mailbox notice, zero cost and no money movement, API key requirement, and exact idempotent outcome strings (not_watching vs unwatched). None of that is derivable from readOnlyHint=false / idempotentHint=true, and it is fully consistent with the annotation that this is a non-destructive mutation.

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 action, then cost/safety facts, then idempotency semantics, then args, then the REST twin. Dense but nearly every clause carries distinct information; the parenthetical '(API key required)' and REST twin line are the least essential.

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?

For a two-param mutation with no output schema, the description covers safety, cost, idempotency, and parameter defaults. Return details are delegated to benchmark_watch rather than enumerated, which requires a cross-lookup but is a reasonable pointer given both tools share a shape.

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%, so the baseline is 3. The description's arg summary ('slug defaults to the routed benchmark, agent_id optional') restates what the schema already documents rather than adding new formats or constraints.

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 opens with a specific verb+resource: 'Stop watching a benchmark'. It is unambiguously the inverse of benchmark_watch and distinct from benchmark_watches (enumeration), and it even names its counterpart when describing the return shape.

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?

The context of use is clear and the no-op case is spelled out ('with no watch it answers watching=false, reason=not_watching, never an error'), which tells an agent it is safe to call defensively. It does not explicitly route to a sibling for the 'show me my watches first' case, so it stops short of full when/when-not 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