Skip to main content
Glama
dkaleganov

Mercury Multiorg MCP

by dkaleganov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_cards

Read-onlyIdempotent

Retrieve card details including status, limits, budgets, and locks. Filter by account or status to find card IDs for further operations.

Instructions

List cards: last four, name on card, nickname, kind, type, status, limits, budgets, locks.

    Use this to find card ids or filter cards by account or status; use
    `get_card` when you already have a card id and `list_merchants` for
    the merchants a lock can name. `account_id` takes one id although
    Mercury's filter accepts several; an unknown `status` is passed
    through and rejected by Mercury with a 400; `limit` counts cards after
    both filters. The API never returns PAN or CVC here; expiry is dropped
    too. Card holder identity is the name on the card and the user id
    only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum cards to return.
entityYesExact `entity` key from `list_entities`, not its `display_name`. Required; there is no default.
statusNoRestrict to one status.
account_idNoRestrict to one account id (from `list_accounts`). Omit for all.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.6
    • changedInput schema / properties / account_id / description
      Previous value: -"Restrict to one account id. Omit for all."New value: +"Restrict to one account id (from `list_accounts`). Omit for all."
    • 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 / status / description
      Previous value: -"Restrict to one status: active, frozen, cancelled, inactive, expired, suspended."New value: +"Restrict to one status."
  2. First observedv0.1.4

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds that the API never returns PAN, CVC, or expiry, which is important security context. It also explains the parameter passing behavior for `account_id` and status, but doesn't mention pagination or rate limits. Since annotations cover safety, this is strong.

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 efficient, with the core purpose and return fields in the first line, followed by usage notes. It is not overly verbose, but some redundancy exists (e.g., repeating the return fields). Still, it is well-organized and front-loaded.

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?

The tool is a list operation with moderate complexity, and annotations plus output schema cover basic expectations. The description adds key usage constraints and security notes. It doesn't mention pagination or error handling for `limit`, but given the output schema and annotations, it is sufficiently complete for most agent use cases.

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 all parameters are described in the schema. The description adds contextual value: `account_id` takes only one id but Mercury accepts several, and `limit` counts after filters. These nuances are not in the schema, so the description enhances parameter understanding.

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 lists cards and enumerates the fields returned. It also distinguishes itself from `get_card` and `list_merchants`, so there is no ambiguity about its purpose.

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?

Explicitly instructs to use `get_card` when a card id is already known and `list_merchants` for merchants referenced by locks. It also notes that `account_id` takes only one id despite the API accepting multiple, and that unknown statuses are passed through to error. This is clear when/when-not guidance.

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