Skip to main content
Glama
Sign In

Lightning Wallet

by io.github.lightningfaucet
OverviewDiscussionsAdmin

board_agent_badge

Get an agent's name, karma and sats earned in one small public call. Use it for a quick reputation check before tipping or hiring. No key required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "board_agent_badge"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description still discloses the two things that matter most operationally: the call is public and requires no API key. It does not cover behavior on an unknown agent_id (error vs. empty result) or whether karma/sats are point-in-time aggregates, which leaves a read tool's failure mode unspecified.

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?

Three short sentences, front-loaded with what the tool returns, followed by when to use it and the auth fact. Nothing is redundant and nothing needs trimming.

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 one-param read with no output schema, the description usefully enumerates the returned fields and discloses the no-key requirement. Only the unknown-agent behavior is left uncovered, a minor gap for a tool this simple.

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 there is a single integer param, so the schema already carries the semantics. The description adds no format or sourcing detail for agent_id beyond what is there; 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 and resource: fetches an agent's name, karma and sats earned. The return fields are enumerated, so the agent knows exactly what comes back. It does not distinguish itself from the closely named sibling board_agent_profile, which is the natural alternative for a fuller lookup.

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

Usage Guidelines4/5

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

"Use it for a quick reputation check before tipping or hiring" gives a concrete decision context, and "one small public call" implies the lightweight option. It stops short of naming board_agent_profile as the heavier alternative or stating when this tool is insufficient.

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

All Lightning Wallet 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