Skip to main content
Glama

agent-exec

One JSON-RPC call with no provider account (paid, x402)

rpc_call

PAID: one blockchain JSON-RPC call on base, base-sepolia, ethereum, solana for $0.0100, no provider account: you name chain and method, we pick the node. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply.

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

Input Schema

NameRequiredDescriptionDefault
idNoYour own call id, echoed back: a string of at most 64 chars or a safe integer. Omitted means we supply one.
chainNoWhich chain to ask: one of base, base-sepolia, ethereum, solana. You never name a URL -- we pick the endpoint, e.g. base.
methodNoThe JSON-RPC method, e.g. eth_blockNumber. Reads, fee queries and raw-transaction broadcast only: 19 EVM methods, 14 Solana. Anything else is refused.
paramsNoThe method's params, as the node takes them; at most 8192 serialized bytes. Omit for a method that takes none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, which is thin for a payment-gated tool. The description supplies behavior the annotations cannot: the price, the two-step unpaid-then-pay flow, accepted payment chains, and a note that feedback is fire-and-forget ('no individual reply'). It does not describe failure or refusal behavior (deferred to the schema's 'Anything else is refused') or rate limits, so not a 5.

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 'PAID', the price, and the no-account premise in the first sentence, which is exactly the right ordering for an agent deciding whether to call. The payment-chain list and the trailing feedback sentence are somewhat dense and tangential, but every sentence carries usable information.

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 four-parameter, no-output-schema tool, the definition covers cost, payment mechanics, chain scope, and the accountless model, which is what an agent needs before spending money. The main remaining gap is what a successful response looks like and how refusals surface, but with a fully documented schema this is close to complete.

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 chain enumeration, the 64-char id echo, the 8192-byte params cap, and method restrictions are all already documented. The description reinforces the chain-versus-URL division ('you name chain and method, we pick the node') but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 specific verb and resource ('one blockchain JSON-RPC call'), names the four supported chains, states the price ($0.0100), and frames the key differentiator ('no provider account: you name chain and method, we pick the node'). An agent can tell immediately this is a single paid RPC proxy rather than a general execution tool like 'execute' or 'check_address' among the siblings.

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?

It gives a concrete invocation protocol: call unpaid to get the price, then resubmit with x402 payment in _meta['x402/payment'] and call again. That is clear operational context. It stops short of naming an alternative tool for non-RPC needs or stating when to avoid this tool, so it is strong but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.