Skip to main content
Glama
Sign In
@jbctechsolutions/mcp-mercury

@jbctechsolutions/mcp-mercury

by jbctechsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_transaction

Access a specific transaction's details from a Mercury bank account by providing the account ID and transaction ID.

Instructions

Get a single transaction by ID for a Mercury account.

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

Input Schema

NameRequiredDescriptionDefault
account_idYesMercury account ID (UUID)
transaction_idYesTransaction ID (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the tool 'gets' a transaction, with no disclosure of error states (e.g., what happens if ID not found), rate limits, or idempotency. The behavioral insight is very limited.

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 a single, well-structured sentence with no redundant or extraneous information. It is appropriately concise for a simple getter tool.

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

Completeness3/5

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

Given the tool is a simple single-resource fetch with no output schema, the description provides the core purpose but lacks context about error handling, return format, or usage scenarios. It is minimally adequate but not rich.

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% for the two parameters, and the description does not add new meaning beyond the schema's own descriptions. It states the tool is for a Mercury account, which aligns with account_id, but that is already implied by the parameter name.

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 tool retrieves a single transaction by ID for a Mercury account, using a specific verb and resource. It effectively distinguishes from siblings like list_transactions (multiple) and get_account (different resource).

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 such as list_transactions. The description does not specify prerequisites, nor does it mention when not to use it (e.g., for batch retrieval).

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