StellarMCP

stellar_fund_account

Fund a Stellar testnet account with 10,000 testnet XLM via Friendbot by providing the account's public key.

Instructions

Fund a Stellar testnet account with 10,000 testnet XLM using Friendbot.

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": {
      "publicKey": "<publicKey>"
    },
    "name": "stellar_fund_account"
  }
}

Input Schema

Name	Required	Description	Default
`publicKey`	Yes	Stellar account public key (G...)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.9Jun 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the operation's effect (crediting 10,000 testnet XLM), the network (testnet), and the mechanism (Friendbot), which is sufficient for such a simple tool. It does not mention Friendbot rate limits or behavior for already-funded accounts, but these are not critical for correct invocation.

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

Conciseness5/5

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

One sentence with no fluff; the key information—action, network, amount, and mechanism—is presented directly. High information density with zero wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with a single parameter and no output schema, the description plus schema is fully sufficient: an agent knows what to pass, why, and what will happen. There are no hidden complex behaviors or sibling ambiguities.

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?

The input schema fully documents the one parameter and its format, and schema coverage is 100%. The description adds no additional parameter detail, but none is needed for a single publicKey argument.

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 names a specific action ('Fund'), a specific resource ('Stellar testnet account'), an exact amount (10,000 testnet XLM), and the mechanism (Friendbot). It is unmistakably distinct from all sibling tools, none of which mention funding, Friendbot, or testnet XLM.

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?

The description clearly situates the tool for testnet account funding via Friendbot, so an agent knows the network context. It does not explicitly name alternatives or state when not to use it, but the context is sufficiently clear among the large sibling set.

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