Skip to main content
Glama

AINDEX

Where to send an agent money, and what has arrived

agent_funding
Read-only

An agent's wallet address on Robinhood Chain, what it holds now (ETH and USDG), how to fund it, where money out goes, and whether Lighter's one-time setup waits for the owner. Use after create_agent to tell the person when a deposit landed.

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": "<agent>"
    },
    "name": "agent_funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint=true annotation already tells the agent this is a safe read, so the description only needs to add context — and it does, disclosing the chain (Robinhood Chain), the two tracked assets, and that Lighter's one-time setup may wait on the owner. It does not say whether results are live or cached, or how current the balances are, which matters for a status tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is no filler, but the opening sentence is a run-on that crams five distinct capabilities (address, holdings, funding path, outbound destination, Lighter setup) into one clause chain. It is not front-loaded around the primary action, so an agent must parse the whole sentence to extract the core purpose.

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?

With no output schema present, the description must convey the return surface, and it does list the categories of information returned. What remains missing is freshness/liveness of balances, response shape, and the polling guidance implied by "when a deposit landed" — the points that matter most for a deposit-monitoring use case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single `agent` parameter has 0% schema description coverage, so the description carries the full burden and fails to compensate: it never explains that the value is an agent identifier matching the p_ pattern, nor how to obtain one. With only one parameter this is a limited gap, but the description adds no meaning at all beyond the schema.

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 enumerates concrete content: the agent's wallet address on Robinhood Chain, current ETH and USDG holdings, funding instructions, outbound address, and Lighter setup status. That is specific enough for an agent to know what it gets back. It lacks a single verb+resource framing and reads as a bundle of several queries rather than one operation, which keeps it below a 5.

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?

"Use after create_agent to tell the person when a deposit landed" gives one clear trigger, so usage is implied rather than left entirely to inference. However, it never clarifies whether this is a one-time fetch or something to poll as a deposit watch, and it names no alternative or exclusion among siblings such as fund_claim or fund_redeem.

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.

Resources