Mercury Multiorg MCP

Overview Schema Source Related Servers Discussions Admin

list_merchants

Read-onlyIdempotent

List priority merchants (id and name) to choose a merchant for card locks. Use case-insensitive search to filter matches before paging.

Instructions

List priority merchants (id and name) usable for card merchant locks; not a transaction's merchant data.

    Use this to pick a merchant for a card lock (the same id/name shape
    appears as `merchantLock` on cards); use `list_transactions` for a
    card transaction's own `merchant` field. `search` is applied by
    Mercury before paging, so `limit` caps the matches.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum merchants to return.
`entity`	Yes	Exact `entity` key from `list_entities`, not its `display_name`. Required; there is no default.
`search`	No	Case-insensitive merchant name filter.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field 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."

First observedv0.1.4Sep 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description does not need to restate safety. It adds valuable behavioral context beyond annotations: `search` is applied "by Mercury before paging" so `limit` caps the matches, and the id/name shape matches `merchantLock` on cards. This helps the agent reason about results without extra calls.

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?

Every sentence earns its place: scope and output shape, intended use case, sibling distinction, and search/paging behavior. The content is front-loaded with the most decision-relevant fact and contains no filler or repetition of schema details.

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?

Given the annotations, full schema coverage, and an output schema, the description covers what an agent needs: what the tool returns, why to use it, when not to use it, and how search/paging behave. There are no obvious gaps that would cause an agent to misinvoke it.

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, and the description adds meaningful extra semantics about how `search` and `limit` interact: search is applied before paging, so limit caps the matched results. It also reinforces the domain semantics by connecting the returned id/name shape to card merchant locks, going beyond the schema's parameter descriptions.

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 and resource: "List priority merchants (id and name)" and immediately scopes it to "card merchant locks." It actively distinguishes itself from list_transactions by stating it is "not a transaction's merchant data," so an agent can tell siblings apart 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?

It gives an explicit when-to-use instruction: "Use this to pick a merchant for a card lock" and names the alternative path: "use list_transactions for a card transaction's own merchant field." It also clarifies that the output shape matches `merchantLock` on cards, removing ambiguity about which field the returned ids map to.

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