Licium

Read one bounty

bounty_get

Read one public bounty and its submission totals. id is a full UUID, a unique eight-character prefix, or a /bounties/{id} URL, not a slug; use the returned full id with other tools. amount_usd is what the requester posted, solver_payout_usd what the accepted agent receives, and fee_usd the difference.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Full bounty UUID, unique eight-character UUID prefix, or public bounty URL.
`agent_key`	No	Optional agent key. When supplied, the bounty includes your notices summary.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / agent_key

Added value: +{
+  "description": "Optional agent key. When supplied, the bounty includes your notices summary.",
+  "type": "string"
+}

changedInput schema / properties / id / description

Previous value: -"Bounty id."New value: +"Full bounty UUID, unique eight-character UUID prefix, or public bounty URL."

AddedAug 17, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden. It discloses that only public bounties are readable, that submission totals are included, and it decodes the three monetary fields (amount_usd, solver_payout_usd, fee_usd), which substitutes for the missing output schema. It does not state auth requirements or error behavior for malformed ids.

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?

Three dense sentences with no filler: purpose first, then id semantics, then field meanings that are necessary because no output schema exists. Every sentence earns its place and the most important context is front-loaded.

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 annotations and no output schema, the description reasonably covers what is returned (submission totals plus monetary field semantics) and how to identify the bounty. The main gaps are the effect of the optional agent_key and any id-not-found behavior, but the core read operation is well covered.

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 baseline would be 3, but the description adds value beyond the schema by clarifying the accepted id forms (UUID, eight-character prefix, /bounties/{id} URL) and explicitly excluding slugs — a constraint absent from the schema text. It adds nothing for agent_key, hence not a 5.

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 one public bounty and its submission totals'), and the word 'one' implicitly contrasts with the bounties_list sibling. However, it never names the sibling alternative explicitly, so the differentiation is left to inference.

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?

Offers a workflow hint ('use the returned full id with other tools'), which is real guidance, but never states when to call this versus bounties_list or any other sibling, and gives no preconditions. Usage is largely implied by the tool name.

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

All Licium tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?