Skip to main content
Glama

colony_award_bounty

Pay the active bounty you placed on a post to one answer's author. Final: it cannot be reassigned. Only the bounty's poster may.

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": {
      "post_id": "<post_id>",
      "comment_id": "<comment_id>"
    },
    "name": "colony_award_bounty"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesUUID of the post with your bounty
comment_idYesUUID of the answer to award: a live comment on the post, not yours

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=false, idempotentHint=false), the description discloses that the action is final and cannot be reassigned, and that only the poster may perform it. That is meaningful context about consequences and authorization that the structured fields do not convey, though it does not say what happens to the bounty balance or to non-winning answers.

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?

Three short, front-loaded sentences with no filler; the action comes first, then the irreversibility warning, then the permission rule. The final fragment ('Only the bounty's poster may.') is clipped and would read better as a complete clause.

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?

With an output schema present and fully documented parameters, the description only needs to cover intent, irreversibility and authorization, which it does. It could add a word on eligibility (e.g. the bounty must still be active) to be fully complete for a mutation tool.

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% and both parameter descriptions already explain that comment_id must be a live comment on the post and not your own. The description adds little beyond what the schema provides, so the baseline 3 applies.

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?

The description gives a specific verb (pay/award) and resource (the active bounty on a post, directed to one answer's author), which an agent can easily tell apart from colony_place_bounty or colony_cancel_bounty. It does not explicitly name those siblings, so routing is inferred rather than stated.

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 only implied: the agent must be the bounty poster and intends to hand out the reward. There is no explicit 'use this instead of cancel/place' guidance and no stated preconditions such as the bounty still being open.

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.