Skip to main content
Glama
Sign In

agentcard

by sh.agentcard
OverviewDiscussionsAdmin

buy_unlink_merchant

DestructiveIdempotent

Disconnect a merchant — drops the saved session + link. The user must re-link (e.g. hosted connect) before shopping it again.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "merchant": "<merchant>"
    },
    "name": "buy_unlink_merchant"
  }
}

Input Schema

NameRequiredDescriptionDefault
merchantYesMerchant slug to disconnect (e.g. doordash).

Output Schema

NameRequiredDescriptionDefault
statusNoOutcome: 'unlinked', 'not_linked', or 'error'.
messageYesHuman-readable unlink outcome.
merchantNoThe merchant slug that was unlinked (or attempted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Description adds behavioral context beyond annotations: explains that the session and link are dropped and that re-linking is required. Aligns with destructiveHint=true without contradiction.

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?

Extremely concise—one sentence that conveys purpose, effect, and required follow-up. 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?

For a simple disconnect tool with one parameter and an output schema, the description fully covers purpose, behavior, and post-conditions. No gaps.

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?

Single parameter 'merchant' has schema description. Description adds a concrete example ('e.g. doordash'), providing clarity beyond the schema.

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 the action (disconnect a merchant) and the resource (merchant). Explains what happens: drops saved session and link, distinguishing it from other merchant-related tools.

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?

Explicitly states the consequence and the need to re-link, guiding the agent on when to use. Lacks explicit when-not-to-use or comparative alternatives, but the context is clear.

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

All agentcard toolsInspect
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