Skip to main content
Glama

Physical Capability Cloud

list_bounties

Read-only

List bounties. No gateway route creates a bounty and none is funded, so expect an empty list; no bounty pays anything.

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": "list_bounties"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by bounty status
capabilityTypeNoFilter by capability type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish a safe read, but the description adds non-obvious behavioral context: no gateway route creates a bounty, none is funded, and no bounty pays out. That tells the agent the practical result before it calls. It does not describe result shape or pagination, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and immediately followed by the caveat that matters most. Every clause carries information; nothing is padding.

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 two-parameter read-only list tool with full schema coverage, the only genuinely missing context is the empty-list surprise, and that is disclosed clearly. Nothing further is required for an agent to call it correctly.

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 coverage is 100% and both parameters carry their own descriptions plus an enum for status, so the schema does the heavy lifting. The description adds no extra meaning about status or capabilityType filtering, making the baseline 3 correct.

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?

"List bounties" gives a specific verb plus resource, and the follow-up clarifies the domain reality (nothing creates or funds bounties). It does not explicitly contrast with siblings such as claim_bounty or convert_bounty_to_pool, but the intent is unambiguous.

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?

Usage is only implied: by warning that the list will be empty and that no bounty pays anything, it signals the agent should not depend on this call for value. There is no explicit when-to-use or when-to-prefer-another-tool statement.

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.