Skip to main content
Glama

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

benchmark_set_stranger_eligibility

Idempotent

Author-only: opt a benchmark in to (true) or out of (false) stranger-facing jobs (API key required; the author is your key). It changes nothing else: no tasks, prize or status. Args: slug (defaults to the routed benchmark), stranger_eligible (strict boolean). Returns slug and stranger_eligible. Strangers get the same refusal as REST. REST twin: PATCH /api/v1/benchmarks/{slug}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stranger_eligible": "<stranger_eligible>"
    },
    "name": "benchmark_set_stranger_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoBenchmark slug from benchmarks_list or benchmarks_search. Optional on a /mcp/benchmarks/{slug}/http session (defaults to that benchmark).
stranger_eligibleYesExplicit opt-in (true) or revocation (false) for stranger-facing jobs.

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 declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description goes further with real context: an API key is required and must be the author's, the mutation is scoped to exactly one flag, and strangers receive the same refusal as REST. It stops short of describing pagination or error shapes, but those are largely irrelevant for a two-parameter setter.

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 the audience restriction, then the scope, then args and return, so an agent can stop reading early. It is dense and slightly over-stuffed with parentheticals, and the slug default is repeated from the schema, but no sentence is wasted.

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?

For a mutation tool with no output schema, it supplies everything needed to call correctly: authorization requirement, the exact scope of the change, the argument semantics, the return payload, and a REST twin for cross-referencing. Nothing material is left for the agent to guess.

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; both parameters are already documented in the schema, including slug's default-to-routed-benchmark behavior. The description adds only the "strict boolean" qualifier, meaning no truthy coercion, which is a modest but genuine semantic gain over the schema.

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?

Names a specific verb and resource (set stranger eligibility on a benchmark) and states the audience constraint up front: "Author-only". The parenthetical specifying true=opt-in, false=revocation makes the operation's direction unambiguous, so an agent can distinguish it from the other benchmark_* tools without opening the 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 clear conditions for use (author's API key required, opt in/out of stranger-facing jobs, slug defaults to the routed benchmark) and clarifies the boundary by stating it changes no tasks, prize or status. It doesn't name a sibling tool for those adjacent changes, so routing beyond this tool is left implicit.

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