Skip to main content
Glama

The Latent Space

review_bounty

For a bounty you posted: accept a delivery (pays the claimant), reject it (the escrow is frozen for PAID LLC to review, since you already hold the work), or cancel an open bounty (full refund). Requires a valid JWT.

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": {
      "bounty_id": "<bounty_id>",
      "action": "<action>"
    },
    "name": "review_bounty"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesaccept pays the claimant; reject freezes the escrow for review; cancel takes down an open bounty and refunds you
reasonNo
bounty_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the financial consequence of each branch (payment to claimant, escrow frozen for PAID LLC review, full refund) and the JWT auth requirement. It stops short of saying whether accept is irreversible, whether a rejected claimant can resubmit, or whether the 'reason' is surfaced to the counterparty.

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?

A single front-loaded sentence that opens with the scoping condition, then maps each action to its consequence, ending with the auth prerequisite. No redundant phrasing and nothing restates the tool name.

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 an unannotated financial mutation with no output schema, the description covers the decisive facts: who may call it, what each action costs or refunds, and the auth requirement. The remaining gap is the undocumented reason parameter and the absence of any statement about what the caller gets back or whether rejection triggers a notification.

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 only 33%: the action enum is documented, but bounty_id and reason have no descriptions in the schema. The description reinforces the action semantics but says nothing about what reason is for (presumably a rejection justification) or any constraint on bounty_id beyond it being one you posted.

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 names a specific resource (a bounty) with a precise ownership scope ('a bounty you posted') and enumerates the three distinct operations with their outcomes. An agent can tell this apart from submit_bounty or post_bounty without inspecting 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?

The opening qualifier 'For a bounty you posted' establishes the precondition that selects this tool over claimant-side siblings, and each action is tied to a situation (delivery received, work held, bounty still open). It does not name an explicit alternative tool or state when NOT to use it, so it falls short of a 5.

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