Skip to main content
Glama
Sign In
ucp-mcp-server

ucp-mcp-server

by nguthrie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ucp_discover

Discover a merchant's UCP capabilities and supported payment methods. Returns protocol version, capabilities list, and accepted payment handlers.

Instructions

Discover a merchant's UCP capabilities and supported payment methods.

Args: merchant_url: The base URL of the UCP-enabled merchant (e.g., http://localhost:8182)

Returns: Dictionary containing: - capabilities: List of UCP capabilities the merchant supports - payment_handlers: List of payment methods accepted - ucp_version: The UCP protocol version

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_url": "<merchant_url>"
    },
    "name": "ucp_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
merchant_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It explains the input and output but does not mention side effects, auth requirements, or error conditions. 'Discover' suggests a read-only operation, but this is not explicitly stated.

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 concise with three distinct sections (summary, args, returns), front-loaded with the purpose, and contains no redundant or irrelevant information.

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 description covers the input parameter and return values sufficiently, and an output schema exists. However, it could mention potential failures (e.g., if the merchant is not UCP-enabled) or error handling.

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

Parameters5/5

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

The description adds meaning to the single parameter 'merchant_url' by explaining it as 'The base URL of the UCP-enabled merchant' and providing an example, compensating for the 0% schema description coverage.

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 'Discover' and resource 'a merchant's UCP capabilities and supported payment methods', clearly distinguishing it from sibling tools like ucp_checkout_create which focus on checkout operations.

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 implies this tool is the first step for interacting with a UCP merchant, but it does not explicitly state when to use it versus alternatives or when not to use it.

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