Skip to main content
Glama
Sign In
CigalPay MCP Server

CigalPay MCP Server

Official
by cigalpay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get a payment

get_payment
Read-only

Retrieve payment status, coin, amounts, and transaction details by payment ID to verify if a crypto payment is confirmed or finished.

Instructions

Status, coin, amounts and transaction of a payment by its id. Paid means status confirmed or finished.

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": {
      "payment_id": "<payment_id>"
    },
    "name": "get_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
payment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description does add real domain semantics — 'Paid means status confirmed or finished' disambiguates a status value that would otherwise be guessed — but says nothing about behavior when the id is unknown or whether the lookup hits an external network.

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, both earning their place: the first states what is returned, the second defines the 'Paid' status. The first sentence is a noun-phrase fragment rather than a clause, which slightly reduces readability.

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?

With no output schema, the description is the only source of return shape and it lists the fields only loosely (status, coin, amounts, transaction) without types or structure. For a simple read-by-id tool this is close to adequate, but the not-found behavior and id format remain unaddressed.

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 coverage is 0% and the single parameter has only a minLength constraint, so the description carries the burden of explaining payment_id. It identifies the argument as a payment id, which is useful, but gives no format, prefix, or example to distinguish a payment id from an order id.

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?

Names the resource (a payment) and the lookup key (its id), and enumerates the returned facts: status, coin, amounts, transaction. The phrase 'by its id' implicitly distinguishes it from the sibling get_payments_by_order, though it never names that sibling 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?

Usage is only implied: call this when you hold a single payment id. There is no statement of when to prefer it over get_payments_by_order or list_active_payments, and no prerequisites or exclusions are given.

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