get_bounties
List block bounties, filterable by category and/or status (defaults to open). Costs 0.5 credits.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| status | No | ||
| category | No |
PromptDNA
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the credit cost (0.5 credits), which is a behavioral trait. However, with no annotations, it fails to mention read-only nature, potential side effects, or performance implications. Partial disclosure.
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 two sentences with no redundant information. It front-loads the primary purpose and adds cost information efficiently.
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?
Given no output schema and low schema coverage, the description covers basic functionality but omits details like return format, pagination (limit parameter), or valid filter values. Adequate but not comprehensive.
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?
The description explains that filtering by category and/or status is possible, adding meaning beyond the schema. However, it does not specify valid values for 'category' or 'status', leaving ambiguity. The schema has 0% description coverage, so the description partially compensates.
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 clearly states the action ('List block bounties'), the resource, and filtering options. It distinguishes the tool from its siblings by being specific about what it lists.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'get_block' or 'get_trending'. Missing context about prerequisites or typical usage scenarios.
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.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a distinct action or resource. For example, compose_prompt assembles prompts, search_blocks searches, register_agent initiates registration. Even related tools like get_block and get_block_versions are clearly differentiated by purpose (current vs history).
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., compose_prompt, submit_block, verify_registration). No mixing of naming conventions, making it predictable for an agent.
Tool Count4/5
With 20 tools, the scope is broad but well-justified by the diverse functionality (search, submission, ratings, registration, DMCA, etc.). It is on the higher end but not excessive for a full-featured platform.
Completeness3/5
The tool set covers core workflows like searching, viewing, creating, and rating blocks, but lacks update or delete operations for blocks. Also missing tools for managing user profiles or block editing, which are notable gaps.