Skip to main content
Glama

Get Transaction

monei_get_transaction
Read-onlyIdempotent

Check any single transaction's full details and current status by entering its reference string. Ideal for answering 'what is the status of TXN_...?' queries.

Instructions

Returns the full details of a single transaction by its reference string.

Use this when the user provides a specific transaction reference and wants to know its current status or details. For browsing recent activity, use monei_get_transaction_history instead.

Args:

  • reference (string): Transaction reference returned from a previous operation (e.g. "TXN_abc123xyz")

Returns: { "id": string, "reference": string, "type": string, "nature": string, "amount": number, "currency": string, "status": string, "narration": string | null, "metadata": object | null, "createdAt": string, "updatedAt": string }

Examples:

  • "What's the status of transaction TXN_abc123?" -> reference="TXN_abc123"

  • "Show me the details for ref_456xyz" -> reference="ref_456xyz"

Error handling:

  • Returns error if the reference does not exist or belongs to a different user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referenceYesTransaction reference string returned from a previous operation

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.3.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond those annotations: it returns full details in a specified shape, supports current status lookup, and includes an error-handling note for nonexistent references.

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?

The description is well-structured and front-loaded: purpose first, then usage guidance, then parameters, return shape, examples, and error handling. Each section earns its place and there is no redundant filler.

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 simple one-parameter read-only tool, the description is complete: it explains when to use it, what it returns, includes the return fields, gives examples, and notes error behavior. The annotations cover safety, and the schema covers the parameter definition.

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 coverage is 100%, so the schema already documents the reference parameter. The description adds value beyond the schema by providing concrete example values like 'TXN_abc123xyz' and natural-language example queries that map to the required reference 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 clearly states a specific verb and resource: 'Returns the full details of a single transaction by its reference string.' It also differentiates itself from monei_get_transaction_history by explicitly noting this tool is for a specific reference, not for browsing recent activity.

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?

Usage is explicitly tied to a concrete user scenario: when the user provides a specific transaction reference and wants status or details. The description also names the alternative tool for browsing recent activity, giving the agent a clear routing decision.

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

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/Mr-Money01/mcp-server'

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