Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

solcheck__balance

SOL balance for a Solana address. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/solcheck/balance

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

Input Schema

NameRequiredDescriptionDefault
addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Solana base58 address"
    • removedInput schema / required
      Removed value: -[
-  "address"
-]
  2. Changed2 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Solana base58 address"
    • addedInput schema / required
      Added value: +[
+  "address"
+]
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose valuable context: a $0.01/call cost in USDC on Base (eip155:8453), the x402 payment payload location, and the GET endpoint that implies a read-only operation. It does not say what happens on payment failure, whether the call is idempotent/cached, or what units the balance is returned in.

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?

Three short clauses, purpose front-loaded, with cost/payment/endpoint compressed tightly. Nothing is padded, though the pricing and URL details could sit in a separate clause rather than a dense run-on.

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 single-parameter read tool with no output schema, the description covers the commercial and transport side well but leaves the response shape unspecified (lamports vs SOL, raw number vs object), forcing the agent to discover the format empirically.

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 0%, so the description needs to compensate; the sole schema field 'address' is never explained (its meaning is only obvious from the name). It does document an out-of-schema parameter, params._meta["x402/payment"], which the schema omits entirely, and that is genuinely additive.

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+resource: 'SOL balance for a Solana address', which is enough for an agent to know exactly what it returns. It does not differentiate from near-siblings such as solcheck__account or chainread__balance, so the agent must infer boundaries from the names alone.

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 by the narrow scope: use it to read a Solana wallet's SOL balance. There is no statement of when to prefer solcheck__account, chainread__balance, or solcheck__token instead, and no mention of preconditions for the address.

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

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