agentcard

buy_list_merchants

Read-onlyIdempotent

List merchants available for agent commerce (Rappi, Good Eggs, DoorDash) and whether this user has linked each one. Link a merchant before shopping it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of merchants returned.
`status`	No	Outcome: 'ok', 'empty', or 'error'.
`message`	Yes	Human-readable merchant list (or an error / empty note).
`merchants`	No	Available commerce merchants and this user's link status for each.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

changedOutput schema / properties / merchants / items / properties / link_status / description

Previous value: -"Whether the user has linked this merchant (e.g. 'linked', 'not_linked')."New value: +"'ready' (no account needed) or 'linked' (account linked): shop now. 'unlinked': no account linked yet. 'pending': a link was started and not finished. 'error': the last link attempt failed."

removedOutput schema / properties / merchants / items / properties / money_path

Removed value: -{
-  "description": "Funding/money path for the merchant, when applicable.",
-  "type": "string"
-}

First observedJul 28, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint safety, so the description mainly adds contextual behavior: it reports merchant availability and per-user linkage status. This is useful but not rich behavioral disclosure beyond what annotations and the presence of an output schema already communicate.

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?

The description is two short, purposeful sentences. It front-loads the core action, gives concrete merchant examples, and ends with the key workflow instruction—no wasted words.

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 zero parameters, a read-only annotation profile, and an output schema, the description provides everything an agent needs to select and call this tool correctly. It covers scope, available merchants, user linkage status, and the prerequisite for shopping.

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?

The tool has zero parameters, so the baseline is 4. The description appropriately focuses on what the tool returns rather than parameter details, and the empty input schema leaves no ambiguity.

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 uses a specific verb ('List'), identifies the resource ('merchants available for agent commerce'), and clarifies the unique value: showing whether the user has linked each merchant. This distinguishes it from sibling tools like buy and buy_unlink_merchant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description clearly situates when to use the tool: before shopping, to see available merchants and whether they are linked. It also gives a practical instruction ('Link a merchant before shopping it') without explicitly naming alternative tools or exclusions, so it stops just short of a full usage guide.

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

All agentcard tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?