Skip to main content
Glama
Sign In
easypaydirect-mcp

easypaydirect-mcp

by praveendias1180
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_transaction

Retrieve a single transaction by its gateway transaction ID. This read-only operation returns the transaction's complete details for query and verification.

Instructions

Fetch a single transaction by its gateway transaction ID. Read-only.

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
transaction_idYesThe gateway transaction ID to look up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses 'Read-only' which is a useful safety trait, but does not mention error behavior, return format, or rate limits. This is acceptable for a simple read operation but lacks depth.

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?

Two short, front-loaded sentences with no redundant words. Every clause contributes to understanding the tool's purpose and safety, making it highly efficient.

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?

Given the tool's simplicity (one parameter, no output schema) and the presence of siblings, the description covers intent and read-only nature sufficiently. Some details like return value or error cases are omitted, but they are not critical for a basic fetch operation.

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 schema description covers 100% of the parameter, already indicating it is the gateway transaction ID. The description adds no new semantics beyond what the schema provides, thus baseline score of 3 is appropriate.

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 the verb 'Fetch' with a specific resource ('a single transaction') and the required identifier ('by its gateway transaction ID'). It distinguishes from sibling tools like search_transactions and list_* tools by emphasizing 'single' and the gateway ID lookup.

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 implies usage when you have a gateway transaction ID and need one specific transaction. It does not explicitly mention alternatives or exclusions, but the context is clear enough to infer appropriate use.

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

Deploy Server

Other Tools