Skip to main content
Glama

IT Security — Access Change Request Recertify — Alder Court Partners (b578285f)

benchmark_set_stranger_eligibility

Idempotent

Author-only: set a benchmark's stranger_eligible curation flag (API key required; the author is your key). Informational since 5753459e r6.2: system-job push stock covers every benchmark open for submission, whatever the flag. 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_eligibleYesCuration flag (true/false). Informational since 5753459e r6.2: system-job push stock covers every benchmark open for submission.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / stranger_eligible / description
      Previous value: -"Explicit opt-in (true) or revocation (false) for stranger-facing jobs."New value: +"Curation flag (true/false). Informational since 5753459e r6.2: system-job push stock covers every benchmark open for submission."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds meaningful behavior beyond the annotations: exactly what is and is not mutated ("no tasks, prize or status"), that strangers receive the same refusal as REST, and what the call returns. The idempotentHint is declared but the description doesn't restate or contradict it, and no rate-limit or failure-mode detail is given, so it is short of a 5.

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 author-only scope, then the caveat, then effects, then args and return. Dense but well-ordered; the revision hash and REST-twin sentence are useful to some agents but add jargon weight that slightly blunts readability.

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?

No output schema exists, and the description compensates by naming the return values (slug and stranger_eligible). Combined with the mutation scope, auth requirement, and default-routing rules, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and the description still adds value by stating the slug default ("defaults to the routed benchmark") and emphasizing a "strict boolean" (no truthy coercion) for the flag. That is real semantic clarification rather than a restatement of titles.

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 ("set a benchmark's stranger_eligible curation flag") and scopes it to a named audience ("Author-only"). No sibling tool in the catalog writes this flag, so the agent can route unambiguously from the description alone.

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 prerequisites (author-only, API key required, "the author is your key") and a strong when-not signal: setting the flag is informational since a named revision, because system-job push stock covers every open benchmark regardless. It stops short of pointing at an alternative tool, so it is clear context rather than full when/when-not routing.

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