Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_get_product

Read-onlyIdempotent

Fetch detailed information about a specific product by its ID to support merchant payment integration and sandbox testing.

Instructions

[Merchant] Get detailed information about a specific product by ID

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": {
      "productId": "<productId>"
    },
    "name": "payware_products_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
partnerIdNoMerchant partner ID (uses PAYWARE_PARTNER_ID env var as default)partner_12345
productIdYesProduct identifier (starts with 'pr')
privateKeyNoRSA private key for authentication (uses environment-specific private key as default)
useSandboxNoUse sandbox environment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered upstream. The description adds essentially nothing beyond that — no note on authentication requirements driven by the privateKey parameter, no rate limits, and no clarification of what 'detailed' returns. The '[Merchant]' prefix is the only extra scoping signal.

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?

A single short sentence with the merchant scope bracketed and the retrieval action front-loaded; there is no redundant wording and nothing to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description could reasonably say what 'detailed information' comprises (which fields, nested resources), but it remains vague. For a simple four-parameter read tool with fully documented schema and rich annotations, this is minimally adequate rather than complete.

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

Parameters3/5

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

Schema description coverage is 100%, so partnerId, privateKey, useSandbox, and the productId pattern are all documented in the schema itself. The description only echoes the 'by ID' lookup, adding no format, default, or environment semantics beyond what the schema provides, which is the expected baseline 3.

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 description gives a specific verb and resource ('Get detailed information about a specific product') plus the lookup key ('by ID'), which distinguishes it from sibling mutations like create_product, update_product, and delete_product. It does not, however, explicitly separate itself from related reads such as get_product_image or get_airing.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many sibling read tools, no mention of prerequisites (e.g., needing a valid merchant partner and key), and no exclusions. An agent must infer usage purely from the tool name and the required productId.

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