Skip to main content
Glama
moolrehq

moolre-mcp

Official
by moolrehq

internal_transfer

Initiate a transfer between Moolre accounts using your account number, currency, amount, and receiver details with a unique external reference.

Instructions

Initiate an internal transfer using your Moolre account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount to transfer.
headersNoHTTP headers to include
currencyYesCurrency code (e.g., GHS).
receiverYesReceiver account or wallet number.
referenceNoOptional narration or reference text.
externalrefYesUnique reference for the transfer.
accountnumberYesYour Moolre Account Number.
Behavior2/5

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

No annotations provided, and the description only states the action. It does not disclose whether the transfer is immediate or scheduled, if it's reversible, or what happens to the source account. For a money movement tool, this is insufficient transparency.

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?

Single sentence with no extraneous text. Front-loaded with the core purpose. Every word earns its place.

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

Completeness2/5

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

Despite 7 parameters including headers and nested objects, no output schema and no annotations. The description is minimal and does not explain expected outcomes, security context (headers imply auth but not explained), or what 'internal' specifically means. Incomplete for a financial transfer tool.

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 coverage is 100% with brief descriptions for each parameter. The tool description adds no extra meaning beyond the schema. Baseline score of 3 is appropriate as the schema does the work, but no value added.

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?

Description clearly states 'Initiate an internal transfer using your Moolre account.' It specifies the action (initiate) and resource (internal transfer), but does not differentiate from sibling tools like 'initiate_transfer' or 'initiate_payment', which could be overlapping.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Given numerous sibling tools related to transfers and payments, the lack of context on when 'internal' applies (e.g., vs. 'initiate_transfer') leaves the agent to guess.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/moolrehq/mcp_php'

If you have feedback or need assistance with the MCP directory API, please join our Discord server