Skip to main content
Glama

AutoTasker Hub — China Social Data API

bounty_list

Active bounty tasks available for claiming. $0.01 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bounty_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoopen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that tasks are active and claimable and mentions '$0.01 USDC', but it does not explain whether this is a reward or a fee, whether authentication is required, how pagination works, or what claiming entails.

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?

The description is extremely concise and front-loads the primary purpose in the first sentence. The second sentence, '$0.01 USDC', is terse to the point of ambiguity about whether it refers to a reward, a fee, or something else.

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

Completeness2/5

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

For a two-parameter listing tool with no annotations and no output schema, the description leaves important gaps: it does not explain return contents, pagination, filtering semantics, or the meaning of the USDC amount. The core purpose is present, but the definition is not complete enough to support confident invocation.

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 description coverage is 0%, and the description does not explain the 'limit' parameter or the 'status' enum values of open, claimed, and all. The word 'active' loosely hints at the default open status, but neither parameter is meaningfully documented beyond the schema itself.

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?

The description identifies the resource as bounty tasks and qualifies them as active and available for claiming, which is specific enough to distinguish a listing tool from unrelated siblings. It lacks an explicit verb such as 'list' and does not differentiate against any close alternative, but the purpose remains understandable.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which alternatives apply for claimed or historical bounties. The phrase 'available for claiming' implies a use case but does not provide actionable selection guidance.

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.