Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_create_schedule

Create a product price schedule to manage time-based pricing using start/end dates and correction rules; Premium plan required.

Instructions

[Merchant] Create a price schedule for a product to manage time-based pricing. 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>"
    },
    "name": "payware_products_create_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateToNoSchedule end date (YYYY-MM-DD format)
dateFromNoSchedule start date (YYYY-MM-DD format)
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
descriptionNoSchedule description
correctionTypeNoPrice correction methodPERCENTAGE
correctionValueNoCorrection value (positive number with max 2 decimals)0.00
priceCorrectionNoPrice correction directionDISCOUNT

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 mutation (readOnlyHint=false), non-idempotency and open-world behavior, so the safety bar is lower. The description adds non-obvious context beyond them: a plan-based authorization gate with a specific failure mode (403). It does not say whether a repeated call creates duplicate schedules or how it interacts with existing schedules.

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?

Two short sentences with zero filler. Purpose comes first and the plan restriction is stated immediately after, before any call is attempted.

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?

For a ten-parameter mutation with no output schema, the description covers purpose and authorization but not what the call returns or what happens to existing schedules. With fully documented parameters and annotations, these gaps are moderate rather than disqualifying.

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 all ten parameters, including the correctionType/correctionValue/priceCorrection enums and date patterns, are already documented in the schema. The description adds no meaning about how those pricing fields combine. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb and resource: 'Create a price schedule for a product to manage time-based pricing.' The verb 'create' plus the 'price schedule' resource distinguishes it from the sibling update/get/delete schedule tools, though it never names them explicitly.

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 precondition: Premium (PRM) plan only, and the server answers 403 on any other plan (for an ISV, the merchant's plan). That is real when-to-use guidance an agent can act on before calling. It stops short of routing between this and update_schedule for existing schedules, or noting overlap rules with existing date ranges.

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