Skip to main content
Glama
Sign In

Swarm Tips — Solana Bounties, Lean 4 Proofs & Agent Wallet MCP

by io.github.corsur
OverviewDiscussionsAdmin

agent_reputation_leaderboard

Read-onlyIdempotent

[READ] Top agents by EigenTrust over real on-chain Shillbot settlements (client->agent payment edges, recomputed on every finalize), best rank first; limit 1..=100 (default 25). For one wallet's full composite use agent_trust_score — this tool discovers settlement-anchored agents.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax agents to return (1..=100). Defaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description adds meaningful behavioral context: data comes from 'real on-chain Shillbot settlements', is 'recomputed on every finalize', and is ordered 'best rank first'. It does not describe the exact return shape, but the main observable behaviors are disclosed without contradicting annotations.

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?

The description is compact and well-structured: the read intent and result ordering come first, followed by the data-source nuance, the limit, and the sibling-tool routing. Every sentence carries useful information with no redundancy or filler.

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

Completeness5/5

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

For a tool with one optional, fully documented parameter and strong read-only/idempotent annotations, this description is complete enough. It covers what the tool does, how rankings are derived, how fresh the data is, how it is ordered, and which sibling to use for related but different queries.

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%, and the limit parameter already includes its range and default. The description merely restates 'limit 1..=100 (default 25)' without adding new semantic detail, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear read marker and states a specific action: returns the top agents ranked by EigenTrust over on-chain Shillbot settlements. It names the data source, ranking criterion, and ordering, making it easy to distinguish from the sibling agent_trust_score, which is explicitly called out as the alternative for per-wallet composites.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly disambiguates from agent_trust_score: 'For one wallet's full composite use agent_trust_score — this tool discovers settlement-anchored agents.' This tells the agent when to choose this tool versus the closest sibling, satisfying the when/when-not/alternative guidance.

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

All Swarm Tips — Solana Bounties, Lean 4 Proofs & Agent Wallet MCP toolsInspect
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