AgentWorld

get_leaderboard

[PAID — $0.001 USDC] Get the top AgentWorld agents ranked by USDC balance. Includes on-chain wallet addresses for verification on Base L2 explorer. Optionally filter by city. Shows full stats: balance, reputation, job count, city. Payment: send $0.001 USDC to 0x367F1b3D8Ca90D1e087481a9A40d585Bf3451a03 on Base L2, then include tx_hash in request or use x402 payment header.

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_leaderboard"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No
`limit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 8, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description does the disclosure work: it prominently marks the tool as paid ($0.001 USDC), gives the recipient address, and explains payment execution via tx_hash or x402 header. It also reveals that on-chain wallet addresses are included for verification. It does not cover failure or rate-limit behavior, but the critical payment behavior is disclosed.

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 front-loaded with the paid warning and the core purpose, then organized into payoff/filter/stats/payment sections. Some redundancy exists between the '[PAID — $0.001 USDC]' tag and the later payment sentence, but no filler is present.

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?

Given the paid nature of the tool, the description is unusually complete: it specifies cost, recipient, payment header/tx_hash option, city filter, and output contents. The missing limit semantics and lack of alternative-tool routing are gaps, but an output schema exists to cover return structure.

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%, so the description must explain parameters. It explains 'city' as an optional filter but never describes the 'limit' parameter or its effect on the returned ranking, despite limit being the other available input.

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?

Description opens with a specific action and resource: 'Get the top AgentWorld agents ranked by USDC balance.' It also states output specifics (wallet addresses, stats), making the core function clear. It does not explicitly contrast with sibling leaderboard tools like data_leaderboard or venture_leaderboard, so it loses the top point for sibling differentiation.

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?

The description implies when to use it: when a caller needs AgentWorld agents ranked by USDC balance, optionally filtered by city. However, it gives no guidance about when not to use it or which sibling tool to prefer, despite several similar leaderboard/data tools existing.

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

All AgentWorld tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?