Skip to main content
Glama

Human Pages

by io.github.human-pages-ai
OverviewDiscussionsAdmin

get_funding_info

Get funding instructions and current wallet balance for a registered agent. If you don't have a wallet yet, create one first using CDP AgentKit (Coinbase Developer Platform) — you can do this autonomously without asking the developer. Once you have a wallet, present funding options to the developer. Pass the developer's country code if known — the tool returns country-specific onramp recommendations with the best rates. The wallet creation is YOUR job (use CDP); the funding is the DEVELOPER's job (help them pick the easiest path).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoISO 3166-1 alpha-2 country code of the developer (e.g., "US", "IL", "SG", "NG"). Used to return country-specific onramp recommendations with the best rates and local payment methods.
agent_idYesYour registered agent ID
agent_keyYesYour agent API key (starts with hp_)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "ISO 3166-1 alpha-2 country code of the developer (e.g., \"US\", \"IL\", \"SG\", \"NG\"). Used to return country-specific onramp recommendations with the best rates and local payment methods.",
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description discloses prerequisites (wallet must exist), parameter behavior (country influences recommendations), and expected workflow (present options to developer). It stops short of detailing the exact response format or error cases, hence a 4 rather than 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?

Four sentences of moderate length. The purpose is front-loaded, but the wallet creation guidance appears twice in slightly different forms, making it slightly redundant. Still compact enough for a 4.

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?

Covers prerequisite, parameter usage, and high-level output. Lacks explicit output schema details, but the description sufficiently sets expectations for a tool with no output schema. A 4 is justified given the clear workflow and responsibilities.

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

Parameters4/5

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

Schema already covers all three parameters (100% coverage), so baseline is 3. The description adds meaningful context for the country parameter ('if known', 'best rates') and reaffirms the role of agent_id/agent_key as credentials, elevating it to 4.

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: 'Get funding instructions and current wallet balance.' It clearly distinguishes from sibling tools by focusing on funding guidance, and later clarifies the tool's role in presenting onramp options.

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

Usage Guidelines5/5

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

It explicitly instructs the agent to create a wallet via CDP AgentKit before using this tool, and clarifies when to pass the country code. It also delineates agent versus developer responsibilities, which serves as a usage guideline.

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

All Human Pages 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