Skip to main content
Glama

Physical Capability Cloud

verify_bounty

Retired: the gateway answers 410 and changes no state. No caller can mark a bounty verified.

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": {
      "bountyId": "<bountyId>",
      "jobId": "<jobId>",
      "score": "<score>"
    },
    "name": "verify_bounty"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob ID that fulfilled the bounty
scoreYesVerification score (0-1)
bountyIdYesBounty ID to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Discloses concrete runtime behavior beyond the annotations: a 410 response and guaranteed absence of state change, which is exactly what an agent needs to avoid a dead call. There is mild tension with readOnlyHint=false, but that hint only declines to assert read-only rather than affirmatively claiming mutation, and the description's explicit "changes no state" is the more informative statement. No return payload details are given, though for a hard-failing endpoint that is minor.

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?

Two short sentences, with the operative fact ("Retired") front-loaded so the agent can stop reading if it only needs the status. Nothing is redundant or padded.

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 retired, mutation-shaped tool with no output schema, the definition covers what matters: it cannot be used and cannot affect state. It lacks a pointer to a supported verification path, which would fully close the loop for an agent trying to complete a bounty.

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%, with bountyId, jobId and score each documented in the schema, so the baseline is 3. The description adds no parameter-level meaning; it only implies the inputs are moot because the endpoint is retired.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Retired" plus "no caller can mark a bounty verified" makes the intended function (marking a bounty verified) and its current disabled status unambiguous, which is enough to separate it from siblings like dispute_verification or claim_bounty. It stops short of a clean positive statement of purpose ("verify a bounty by job and score"), relying on the name to supply the verb+resource.

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 decisive negative guidance: the gateway returns 410 and state never changes, so the agent should not call this tool for any verification workflow. It does not name a working alternative among the verification siblings, which is the main remaining gap.

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.