Skip to main content
Glama
Sofiia7

nadbounty-mcp

by Sofiia7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

list_open_bounties

Read-onlyIdempotent

Browse open NadBounty bounties you can still take or enter, sorted newest first. Find work or survey the market, with reward, deadline, gates, description CID, and offset paging.

Instructions

List open NadBounty jobs that can still be taken or entered, newest first within a page, with reward, deadline, gates and the description CID. Use it to find work or to survey the market; page with offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMost bounties to return per page, 1-100.
offsetNoNumber of open bounties to skip, for paging. 0 starts at the first one.
categoryNoOnly bounties of this category. Omit for all categories (dev, design, content, data, other).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.6.2
    • removedInput schema / properties / agentOnly
      Removed value: -{
-  "description": "If true, only bounties restricted to ERC-8004 agents.",
-  "type": "boolean"
-}
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category. Omit for all categories."New value: +"Only bounties of this category. Omit for all categories (dev, design, content, data, other)."
    • removedInput schema / properties / humanOnly
      Removed value: -{
-  "description": "If true, only bounties restricted to humans.",
-  "type": "boolean"
-}
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 20)."New value: +"Most bounties to return per page, 1-100."
    • removedInput schema / properties / maxReward
      Removed value: -{
-  "description": "Maximum reward in USDC dollars.",
-  "type": "number"
-}
    • removedInput schema / properties / minReward
      Removed value: -{
-  "description": "Minimum reward in USDC dollars.",
-  "type": "number"
-}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of open bounties to skip, for paging. 0 starts at the first one.",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds useful context beyond that: newest-first ordering within a page, and the payload contents (reward, deadline, gates, description CID). It does not mention whether a total count or end-of-list signal is returned, which is a minor gap.

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?

A single dense sentence plus a short usage clause; the what, the ordering, the returned fields and the paging mechanism are all front-loaded with no filler.

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?

For a read-only list tool with no output schema, the description usefully enumerates the returned fields (reward, deadline, gates, CID) and ordering, which is what an agent needs to consume the result. Only the absence of any end-of-list/pagination-completeness hint keeps it from the top.

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 description coverage is 100%, so limit, offset and category are all fully documented in the schema and the baseline is 3. The description only echoes the paging idea ('page with offset') and adds no format or edge-case detail beyond the schema.

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 ('List open NadBounty jobs that can still be taken or entered') plus the ordering and the fields returned, so the agent knows exactly what comes back. It implicitly distinguishes itself from get_my_bounties by scoping to open/public work, but never names a sibling explicitly, which keeps it short of a 5.

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?

'Use it to find work or to survey the market' gives clear intent-based context for when this tool applies, and 'page with offset' tells the agent how to iterate. There is no explicit when-not guidance or named alternative (e.g. get_my_bounties for the agent's own posts), so it stops short of the top band.

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

Deploy Server

Other Tools