Mercury Multiorg MCP

Overview Schema Source Related Servers Discussions Admin

list_events

Read-onlyIdempotent

Retrieve a change-event feed for Mercury accounts and transactions, showing what changed and which fields were affected. Filter by entity, resource type, or time to audit recent activity across organizations.

Instructions

List the change-event feed in Mercury API desc order: what changed on which resource, with the changed fields.

    `mergePatch` / `previousValues` are re-projected through the changed
    resource's own allowlist (so an account event masks the account
    number and a transaction event carries no bank coordinates). The API
    has no time filter and documents no sort key, so with `since` the
    whole feed (Mercury keeps 90 days) is walked, filtered on
    `occurredAt` here, and sorted newest first before `limit` applies;
    `truncated` is then exact. Without `since` the Mercury API `desc`
    order is returned as is. Use this to see what changed recently on
    transactions and accounts and which fields changed; use
    `list_transactions` for the transactions themselves and
    `list_webhooks` for the endpoints subscribed to these events. An
    unknown `resource_type` is a 400 from Mercury.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum events to return (with `since`: newest first; else Mercury API desc order).
`since`	No	Only events at or after this time, YYYY-MM-DD or ISO 8601 (UTC). Events live 90 days.
`entity`	Yes	Exact `entity` key from `list_entities`, not its `display_name`. Required; there is no default.
`resource_type`	No	Restrict to one resource type.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.6Sep 15, 2026

changedInput schema / properties / entity / description

Previous value: -"Entity key from `list_entities`. Required; there is no default."New value: +"Exact `entity` key from `list_entities`, not its `display_name`. Required; there is no default."

changedInput schema / properties / resource_type / description

Previous value: -"Restrict to one resource type: transaction, checkingAccount, savingsAccount, treasuryAccount, investmentAccount, creditAccount."New value: +"Restrict to one resource type."

First observedv0.1.4Sep 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Despite strong annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false), the description adds substantial behavioral context: the mergePatch/previousValues re-projection through each resource's own allowlist (masking account numbers, stripping bank coordinates), the 90-day feed walk with no time filter, the sorting-before-limit behavior that makes `truncated` exact, and the 400 on unknown resource_type. This is genuine value beyond annotations with no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but information-dense; every sentence carries behavioral, ordering, or routing value. It front-loads the core purpose and defers the fine-grained ordering/truncation details. It could arguably be tightened into clearer paragraphs, but there is no filler — it earns its length.

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 complex tool with 4 parameters, non-obvious ordering semantics, and an error case, the description is thorough. It covers the feed-walk behavior, masking rules, truncation exactness, the 400 on unknown resource_type, and usage routing. An output schema exists, so return-value documentation isn't needed from the description; nothing an agent needs to call this correctly is missing.

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 baseline is 3. The description adds meaning beyond the schema: `since` triggers a whole-feed walk filtered on `occurredAt` and sorted newest-first before `limit` applies (making `truncated` exact), and unknown `resource_type` values yield a 400. The `entity` requirement for an exact key is also echoed. This is a clear step above baseline, though some param details remain schema-led.

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 opens with a specific verb+resource: 'List the change-event feed in Mercury API desc order: what changed on which resource, with the changed fields.' This clearly states what is returned and differentiates it from sibling list tools by naming them as alternatives in the usage guidance. An agent can distinguish this from list_transactions and list_webhooks without opening schemas.

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?

The description gives explicit when-to-use and when-not-to-use guidance: 'Use this to see what changed recently on transactions and accounts and which fields changed; use list_transactions for the transactions themselves and list_webhooks for the endpoints subscribed to these events.' It also documents the `since` semantics and the 400 error case, leaving nothing to inference.

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