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

@jbctechsolutions/mcp-mercury

by jbctechsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_account

Retrieve a Mercury account's current and available balances using its account ID.

Instructions

Get a single Mercury account by ID, including current and available balances.

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>"
    },
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesMercury account ID (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. Only mentions inclusion of balances, but fails to disclose read-only nature, idempotency, rate limits, or error conditions. Minimal behavioral insight beyond basic output.

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 conveying purpose and output concisely. No redundant words; every element earns its place.

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?

With one required parameter and no output schema, description adequately states purpose and key output (balances). Could be more complete by hinting at other returned fields (e.g., account name, currency), but sufficient for a simple read 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 description coverage is 100%, with account_id adequately described as 'Mercury account ID (UUID)'. The tool description does not add further meaning beyond the schema, so a 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?

Clearly specifies the action 'Get', the resource 'single Mercury account', and includes distinct output details 'current and available balances'. Distinguishes from sibling tools like list_accounts (plural) and get_transaction (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 Guidelines3/5

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

Implies usage when needing a specific account by ID, but provides no guidance on when not to use it (e.g., for listing all accounts) or alternatives. Lacks explicit context of prerequisites or exclusions.

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