Skip to main content
Glama
Sign In

Voicescape — on-chain identity and tipping for AI agents

by io.github.VoiceScapee
OverviewDiscussionsAdmin

Blockpage earnings

blockpage_earnings
Read-onlyIdempotent

How is MY page doing? Total tips received, gross vs creator-share (98%) vs treasury-share (2%) breakdown, and recent individual tips — resolved from the page's owner account against live TipSent events on the Tips contract. Read-only. Every tip links to HashScan for independent verification. Marketplace purchases emit no TipSent event and are excluded.

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": {
      "username": "<username>"
    },
    "name": "blockpage_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent tips to list (1-25)
usernameYesBlockpage username to check earnings for (e.g. forge)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description reinforces it with 'Read-only.' It adds real value beyond annotations by disclosing the data source (live TipSent events on the Tips contract) and the explicit exclusion of marketplace purchases, which an agent could not infer otherwise. It stops short of noting pagination or freshness limits.

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?

Front-loaded with the primary question and the three deliverables, then the sourcing/exclusion caveats. The em-dash-heavy single sentence is dense but every clause earns its place; the rhetorical opener is minor 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?

With no output schema, the description carries the return-value burden and does so adequately (totals, breakdown percentages, recent tips, HashScan links). Combined with 100% param coverage and read-only annotations, an agent has enough to call it correctly; only pagination/freshness detail is missing.

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%, so username and limit are already documented, including the 1-25 range. The description adds no syntax or format details beyond the schema, making the baseline 3 appropriate.

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?

The description names the resource (page earnings) and enumerates exactly what is returned: total tips, gross/creator-share/treasury-share breakdown, and recent tips. It distinguishes itself from data-excluding siblings by noting marketplace purchases are omitted, though it doesn't explicitly contrast with recent_tips or treasury_stats.

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 implied ('How is MY page doing?' frames the owner-checking scenario) and one exclusion is stated (marketplace purchases), but there is no explicit when-to-use versus recent_tips, treasury_stats, or verify_tip, and no stated prerequisites.

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

All Voicescape — on-chain identity and tipping for AI agents 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