Skip to main content
Glama
Sign In
payping-mcp

payping-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

PayPing: list products

payping_list_products
Read-onlyIdempotent

Retrieve PayPing products from a merchant account with code, title, price in Toman, stock, active status, and payment link. Filter by search text, paging, or archived items.

Instructions

List products (PayPing "financial items"): code, title, price (Toman), stock, active, has a payment link.

Input Schema

NameRequiredDescriptionDefault
limitNoItems to return, 1-50.
offsetNoSkip this many items (paging).
searchNoText to search for.
include_archivedNoInclude archived items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.2.0
    • removedInput schema / properties / include_archived / title
      Removed value: -"Include Archived"
    • changedInput schema / properties / limit / description
      Previous value: -"Items to return, 1-50 (PayPing's maximum is 50)."New value: +"Items to return, 1-50."
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / search / title
      Removed value: -"Search"
    • removedInput schema / title
      Removed value: -"payping_list_productsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "payping_list_productsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered externally. The description adds useful domain context (the items are called 'financial items', prices are denominated in Toman, and items carry a payment link), but says nothing about ordering, pagination total counts, or rate limits.

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?

A single tight sentence with the core action front-loaded before the field enumeration; no filler. It is slightly compressed, packing the return-field list and the terminology alias into one clause, but every element earns its place.

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 partly compensates by naming the returned fields (code, title, price, stock, active, payment link), which is the main information gap for this tool. Paging mechanics and default exclusion of archived items are left to the schema, but nothing critical for a simple list call is missing.

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% – limit, offset, search and include_archived are all self-documented, including ranges and defaults. The description adds no parameter-level detail (e.g. what search matches against, or that archived items are excluded by default), so the 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?

Specific verb (list) plus resource (products), and it disambiguates the domain-specific PayPing term 'financial items' so an agent doesn't confuse products with transaction line items. It also enumerates the returned fields. The sibling payping_get_product (singular retrieval) is only implicitly contrasted via the 'list' verb, so it falls just short of 5.

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 when-to-use guidance: nothing says to reach for this instead of payping_get_product for a single item, nor when to set include_archived or use the search parameter. The description only describes payload contents, leaving routing entirely to inference.

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