Skip to main content
Glama
Sign In
payping-mcp

payping-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

PayPing: create coupon

payping_create_coupon
Destructive

Create an active discount coupon for a PayPing account and return its code. Set percent or fixed Toman discounts, limits, expiry, and product scope; confirm before writing.

Instructions

Create an active discount coupon and return its code. Creates real data: confirm with the user first.

Input Schema

NameRequiredDescriptionDefault
kindYes'percent' off, or a fixed Toman amount off.
nameYes
amountYesPercent (1-100) or Toman, per `kind`.
max_usesNo
expires_onNoLast valid day (YYYY-MM-DD).
coupon_codeNoCode buyers type; omit to generate.
product_codesNoLimit to these products; omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.0
    • removedInput schema / properties / amount / title
      Removed value: -"Amount"
    • removedInput schema / properties / coupon_code / title
      Removed value: -"Coupon Code"
    • removedInput schema / properties / expires_on / title
      Removed value: -"Expires On"
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / max_uses / title
      Removed value: -"Max Uses"
    • removedInput schema / properties / name / title
      Removed value: -"Name"
    • removedInput schema / properties / product_codes / title
      Removed value: -"Product Codes"
    • removedInput schema / title
      Removed value: -"payping_create_couponArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "payping_create_couponDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false. The description adds value on top: it discloses the return value (the generated `code`) and an operational guardrail (confirm with the user). It stops short of explaining coupon lifetime or side effects beyond creation.

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 tight sentences, front-loaded with the core action and followed by the caution. Every clause carries information; nothing is wasted.

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?

With no output schema, the description correctly notes the returned `code`, and rich annotations cover the mutation/safety profile. It is largely complete for a create tool, though it omits parameter-level detail.

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?

The description contributes nothing about the seven parameters. Schema coverage is 71% (below the 80% threshold), leaving `name` and `max_uses` undocumented in both schema and description, so the description fails to compensate for the gap.

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 (create) and resource (discount coupon), plus two key facts: the coupon is active and the response returns its `code`. This clearly separates it from the get_coupon/list_coupons siblings, 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 Guidelines3/5

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

Adds a real usage rule ("Creates real data: confirm with the user first") that tells the agent to gate the call behind user confirmation. However, it gives no guidance on when to create vs. when to reuse or fetch an existing coupon, so usage is only partially covered.

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