Skip to main content
Glama
Sign In

AnchorPad

by fun.anchorpad
OverviewDiscussionsAdmin

My coins and earnings

anchorpad_my_coins
Read-only

A wallet's coins on AnchorPad, their links and unclaimed creator earnings.

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

Input Schema

NameRequiredDescriptionDefault
walletNoThe user's Solana wallet address. Not needed with an agent key (the agent's wallet is used)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, which covers the safety profile, so the bar is lower. The description adds modest context about what is accessed (coins, links, and unclaimed creator earnings) but does not disclose anything further such as response shape or whether earnings data may be zero/stale. No contradiction with annotations.

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?

A single, compact sentence that front-loads the key subject ('A wallet's coins on AnchorPad') and packs the relevant data types (links, unclaimed creator earnings) without waste. Slightly more context would be nice, but it is appropriately sized.

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 read-only, single-optional-param tool with no output schema, the description is mostly adequate but leaves details open: what exactly 'links' refers to, the response shape, and the meaning of 'unclaimed creator earnings' in this context are not specified. An agent gets the gist but not full situational context.

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% for the single parameter, and the schema already explains the wallet address and the agent-key behavior. The description adds little beyond confirming the wallet context ('A wallet's coins'), so the baseline 3 is appropriate when the schema does the heavy lifting.

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 identifies a specific resource (a wallet's coins on AnchorPad) and the exact data returned (links, unclaimed creator earnings), going beyond the title 'My coins and earnings.' It is not a tautology, though the controlling verb is only implied ('view'/'get') rather than stated, and it does not explicitly contrast with siblings beyond content type.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus siblings like anchorpad_prepare_claim, anchorpad_prepare_trade, or anchorpad_pairs. There is no when-to-use context, no exclusions, and no mention of alternatives; an agent must infer the tool's role purely from its name and sibling names.

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

All AnchorPad 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