Skip to main content
Glama

Physical Capability Cloud

get_bounty_leaderboard

Read-only

Get the bounty leaderboard. No gateway route creates or verifies a bounty, so expect an empty list.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of entries to return (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description still adds real behavioral context by warning that no route creates or verifies bounties, so an empty list should be expected — that prevents the agent from misinterpreting an empty result as a failure.

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?

Two short sentences, front-loaded with the purpose. The caveat sentence earns its place by preventing misinterpretation of an empty response, though the phrasing about gateway routes is slightly indirect.

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?

For a one-optional-param read tool with annotations and no output schema, the description covers intent and the empty-list expectation. It does not say what a non-empty entry contains (rank, address, amount) or how ordering works, which matters more given there is no output schema.

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 the single 'limit' parameter already documents its default of 10. The description adds nothing about ordering, pagination, or how limit is applied, so baseline 3 applies.

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 ('Get') and resource ('bounty leaderboard'), so an agent knows this is a read of ranked bounty data. It does not name or distinguish itself from siblings like claim_bounty or verify_bounty beyond the implicit read-only framing.

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: it's a retrieval tool, so an agent can infer it's for reading leaderboard standings. There is no explicit when-to-use, no statement of alternatives for bounty-related queries, and no threshold/ranking criteria mentioned.

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.