Skip to main content
Glama

crossborder_merchant_status

Read-onlyIdempotent

Checks merchant authorization for a cross-border platform connector and returns a structured authorized or unavailable status, so agents can report missing grants instead of errors or empty results.

Instructions

Report merchant-authorization status for a cross-border platform connector.

The inner-ring data channel (store operations, platform bestsellers, after-sales reviews) is merchant-authorization-gated BY DESIGN: the connector reads platform OFFICIAL APIs only, with the merchant's explicit store authorization; scraping is out of contract (triage discipline: never reverse-engineer). Until a merchant completes authorization the tool answers with a structured unavailable (unauthorized) response — never an error object and never a silent empty list, so agents can report 「不可得(未授权)」 verbatim.

Authorized deployments register merchant grants via the FD_CROSSBORDER_MERCHANT_AUTH_JSON env ({"": {"authorized": true, "merchant_id": "...", "scopes": [...]}}); the same response shape then flips to authorized with the granted scopes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crossborder_merchant_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNotiktok_shop

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the bar is lower, yet the description adds meaningful behavior: a structured 'unavailable (unauthorized)' payload instead of an error object or empty list, and an env-var-driven authorization path that flips the response to 'authorized' with scopes. It does not cover caching, rate limits, or behavior under partial scopes, which keeps it from a 5.

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

Conciseness3/5

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

The core behavior is front-loaded and clear, but the middle of the description drifts into justification about scraping being out of contract and 'triage discipline: never reverse-engineer', which is policy commentary rather than invocation guidance. The embedded non-English string is justified since it is the verbatim output, but overall it is longer than the task requires.

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?

An output schema exists, so return values need not be detailed, and the description still explains the two response states an agent must distinguish. Combined with read-only annotations this is nearly complete; the only real hole is the undocumented platform parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'platform' parameter (default 'tiktok_shop'), so the description must compensate. It never mentions the parameter, never lists which platform identifiers are valid, and never says what happens if an unknown platform is passed, leaving the agent to guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line names a specific verb and resource: 'Report merchant-authorization status for a cross-border platform connector,' which tells an agent exactly what the tool returns. It does not differentiate itself from the sibling 'auth_status', so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent is told to call it before reading inner-ring data and to report 'unavailable (unauthorized)' verbatim, which gives some when-to-use context. There is no explicit statement of when NOT to use it, or how it relates to sibling authorization/status tools like auth_status or auth_events.

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