Skip to main content
Glama
klodr

mercury-invoicing-mcp

mercury_list_treasury_transactions

Audit Treasury cash flows and reconcile yield accruals by listing Treasury account transactions like sweeps and dividend accruals.

Instructions

List transactions for a Mercury Treasury account (sweeps, dividend accruals, etc.).

USE WHEN: auditing Treasury cash flows, reconciling yield accruals, or building a Treasury-only ledger view.

DO NOT USE: for deposit-account transactions (use mercury_list_transactions). For IO Credit transactions, use mercury_list_credit_transactions.

RETURNS: { transactions: [{ id, amount, kind, postedAt, ... }] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesTreasury account ID
limitNo
offsetNo
startNoFilter after this date (YYYY-MM-DD)
endNoFilter before this date (YYYY-MM-DD)

Implementation Reference

  • The handler function that executes the tool logic. It calls GET /treasury/{accountId}/transactions with optional query parameters (limit, offset, start, end) and returns the result.
    async ({ accountId, ...query }) => {
      const data = await client.get(`/treasury/${accountId}/transactions`, query);
      return textResult(data);
    },
  • Zod schema defining the input validation for the tool. Accepts accountId (UUID required), plus optional limit, offset, start, and end filters.
    {
      accountId: z.string().uuid().describe("Treasury account ID"),
      limit: z.number().int().min(1).max(500).optional(),
      offset: z.number().int().min(0).optional(),
      start: z.iso.date().optional().describe("Filter after this date (YYYY-MM-DD)"),
      end: z.iso.date().optional().describe("Filter before this date (YYYY-MM-DD)"),
  • Registration via defineTool() which internally calls server.registerTool(). The tool is named 'mercury_list_treasury_transactions' with description, schema, and handler.
    defineTool(
      server,
      "mercury_list_treasury_transactions",
      [
        "List transactions for a Mercury Treasury account (sweeps, dividend accruals, etc.).",
        "",
        "USE WHEN: auditing Treasury cash flows, reconciling yield accruals, or building a Treasury-only ledger view.",
        "",
        "DO NOT USE: for deposit-account transactions (use `mercury_list_transactions`). For IO Credit transactions, use `mercury_list_credit_transactions`.",
        "",
        "RETURNS: `{ transactions: [{ id, amount, kind, postedAt, ... }] }`.",
      ].join("\n"),
      {
        accountId: z.string().uuid().describe("Treasury account ID"),
        limit: z.number().int().min(1).max(500).optional(),
        offset: z.number().int().min(0).optional(),
        start: z.iso.date().optional().describe("Filter after this date (YYYY-MM-DD)"),
        end: z.iso.date().optional().describe("Filter before this date (YYYY-MM-DD)"),
      },
      async ({ accountId, ...query }) => {
        const data = await client.get(`/treasury/${accountId}/transactions`, query);
        return textResult(data);
      },
    );
Behavior3/5

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

No annotations, but description provides a return format hint. However, missing details on pagination behavior, rate limits, or ordering. Adequate but not comprehensive.

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?

Three short paragraphs, front-loaded with purpose, use/when-not. Every sentence adds value. No redundancy.

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?

Covers purpose, usage, return format. Lacks details on pagination defaults or total count. Still fairly complete for a list tool given no output schema.

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 covers 60% of parameters (3 out of 5 have descriptions). Description adds no extra parameter info beyond what is in schema. Baseline score of 3 applies.

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 states it lists transactions for a Mercury Treasury account, with specific examples like sweeps and dividend accruals. Distinguishes from sibling tools by mentioning deposit-account and IO Credit transactions.

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?

Explicit USE WHEN and DO NOT USE sections, providing concrete scenarios and naming alternative tools. Helps agent choose correctly among siblings.

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/klodr/mercury-invoicing-mcp'

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