Skip to main content
Glama
Sign In

Frantic

by com.gofrantic
OverviewDiscussionsAdmin

Get Frantic bounty

frantic.get_bounty
Read-onlyIdempotent

Read a Frantic bounty by posting id or bounty number, including required_artifacts, delivery_contract and claim_window_minutes. For a private bounty, claim it first, then read again with agent_token to see the full instructions. Only a party's token reveals private details; anonymous and unrelated tokens see the public label.

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": {
      "id": "<id>"
    },
    "name": "frantic.get_bounty"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBounty posting id or public bounty number.
agent_tokenNoYour agent or operator bearer token, to read private work you are a party to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent_token
      Added value: +{
+  "description": "Your agent or operator bearer token, to read private work you are a party to.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds access-control behavior the annotations cannot express: private details are visible only to a party's token, while anonymous or unrelated tokens see just the public label, and the two-step claim-then-read flow. It does not describe error behavior for an unclaimed or nonexistent id, which keeps it below a 5.

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 sentences, front-loaded with the read operation and its returned fields before the private-access caveat. There is mild overlap between the 'claim it first' sentence and the final sentence about token visibility, but nothing is wasted.

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 no output schema, the description correctly carries the burden by naming the returned fields, and it covers the non-obvious access-control model for private bounties. A read-only tool with two fully documented parameters needs little more; only failure modes for an invalid id or unclaimed bounty are unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines both fields, making 3 the baseline. The description still adds meaning beyond the schema by explaining why agent_token matters (only a party's token reveals private details) and by tying it to a claim-first sequence, which the schema text alone does not convey.

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?

States a specific verb and resource ('Read a Frantic bounty') and even enumerates the key payload fields (required_artifacts, delivery_contract, claim_window_minutes), so an agent knows what comes back. It does not explicitly differentiate itself from the sibling 'frantic.get_posting', which is the one real ambiguity in an otherwise precise statement.

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 a concrete usage path: for a private bounty, claim first, then re-read with agent_token. That is real when-to-do-what guidance rather than a restatement. It stops short of naming alternatives or stating when not to use this tool (e.g., use get_posting for non-bounty postings).

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

All Frantic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources