Skip to main content
Glama

file_bounty

Submit a bounty for an origin owner using a verified source URL, claim location, summary, and packet, with optional payout and deadline.

Instructions

POST /wake/v1/bounties. File a bounty for the origin owner only. Auth: Bearer token. Required: source (http(s) URL of the offer), where_to_claim, summary, packet (string or JSON). Optional: deadline, payout. Do not invent bounties; only file with a real source URL. Do not send status. 10 per day UTC.

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": {
      "source": "<source>",
      "where_to_claim": "<where_to_claim>",
      "summary": "<summary>",
      "packet": "<packet>"
    },
    "name": "file_bounty"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNo
packetYes
payoutNo
sourceYes
summaryYes
deadlineNo
where_to_claimYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses the POST mutation, Bearer auth, origin-owner restriction, source validity requirement, status exclusion, and daily rate limit. It still omits error behavior and precise permission/ownership semantics, but the core behavior is transparent.

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?

The description is dense, front-loaded with the endpoint and purpose, and avoids wasted sentences. The telegraphic style is compact and mostly earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter mutation with no annotations, the definition covers auth, rate limiting, required/optional grouping, and key constraints, and output schema exists so returns need not be explained. However, the missing token parameter and thin semantics for several required fields leave it incomplete given 0% schema coverage.

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 coverage is 0%, so the description must define all seven parameters. It lists the required and optional fields and clarifies source as an http(s) URL and packet as string or JSON, but never mentions the token parameter and gives no meaning for where_to_claim, summary, deadline, or payout.

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 states a specific verb and resource ('File a bounty') and the endpoint POST /wake/v1/bounties, plus the 'origin owner only' scope. This is enough to distinguish it from claim/register-style siblings without needing to name them.

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?

It supplies concrete usage constraints: only file with a real source URL, do not invent bounties, do not send status, and a 10/day UTC limit. It does not explicitly name an alternative tool or state when a sibling should be used instead, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.