Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_get_audio

Read-onlyIdempotent

Retrieve detailed information about a specific product audio file. Requires a Premium plan; other plans return a 403 error.

Instructions

[Merchant] Get detailed information about a specific audio file. Premium (PRM) plan only: the server answers 403 on any other plan (for an ISV, the merchant's plan).

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>",
      "audioId": "<audioId>"
    },
    "name": "payware_products_get_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioIdYesAudio identifier
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered; the description adds genuinely new behavior by disclosing the plan gate and the exact 403 error condition, including the ISV/merchant nuance. It says nothing about what fields are returned or whether unknown audioIds error vs return empty.

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

Conciseness4/5

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

Two short sentences, front-loaded with the core action and followed immediately by the eligibility constraint. The bracketed [Merchant] prefix is slightly noisy but is scoped tagging rather than filler.

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?

For a read-only getter with no output schema and full schema coverage on inputs, the main missing piece is any indication of what 'detailed information' contains or how missing/inaccessible IDs behave. The authentication and plan gating are sufficiently covered, so the gap is minor rather than blocking.

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 every parameter (audioId, productId pattern, partnerId, privateKey, useSandbox) is already documented in the schema. The description adds no further parameter-level meaning such as format of audioId or what happens with the default sandbox/partner values, so baseline 3 applies.

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?

Description opens with a specific verb+resource: get detailed information about a specific audio file, which distinguishes it from the plural listing sibling get_audios. It stops short of naming that sibling explicitly, so differentiation relies on the singular/plural reading rather than an explicit statement.

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?

Gives a hard usage precondition: Premium (PRM) plan only, with the concrete failure mode (server answers 403 on any other plan, and for an ISV it is the merchant's plan). It does not say when to prefer this over list-level or update/delete audio siblings, but the eligibility rule is clear and actionable.

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