Skip to main content
Glama

Agentizable tool

get_card_bounty_review
Read-onlyIdempotent

Read a card-paid bounty's public review state: the submission awaiting its customer with its decide_by time and whether silence accepts it (auto_accept), each verdict with its reason, appeal and ruling, signed attestations, and appeal_typed_data while a rejection can still be appealed. Names no customer. No authentication.

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": {
      "network": "<network>",
      "bounty_contract": "<bounty_contract>"
    },
    "name": "get_card_bounty_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkYes
bounty_contractYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With readOnly/idempotent/non-destructive hints already supplied, the description still adds real value: "Names no customer" discloses anonymization behavior, "No authentication" discloses the access model, and the conditional "while a rejection can still be appealed" explains why appeal_typed_data may be absent. It stops short of stating behavior for a nonexistent contract or invalid network, but it clears the bar set by the annotations.

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?

The definition is a single front-loaded sentence that opens with the verb and resource before listing returned fields, then closes with two short constraint statements. The field enumeration is dense but every clause names a distinct part of the response, so nothing is redundant; it is marginally long for one sentence.

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?

There is no output schema, and the description compensates well by enumerating the response payload including conditional fields. Combined with the auth/privacy statements, an agent has enough to call and interpret the result; the remaining gap is the unexplained parameter semantics, which is scored separately.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters, so the description carries the full burden and fails to compensate. It never explains what the `network` enum (base-mainnet vs base-sepolia) selects or that `bounty_contract` takes a 0x-prefixed 40-hex address, leaving the caller dependent on the raw schema patterns.

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 uses a specific verb ("Read") plus a precisely scoped resource ("card-paid bounty's public review state") and then enumerates the exact contents returned: pending submission, decide_by, auto_accept, verdicts with reason/appeal/ruling, attestations, and appeal_typed_data. The qualifier "card-paid" implicitly separates it from the managed-bounty siblings such as get_managed_bounty_review. An agent knows exactly what this tool retrieves before 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by "public review state" and by the note that payload appears only "while a rejection can still be appealed," which hints at when the appeal_typed_data is relevant. However, there is no explicit when-to-use framing and no direct routing to alternatives like get_managed_bounty_review or appeal_card_bounty_review, so the agent must infer selection from the adjective "card-paid".

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