Skip to main content
Glama
Sign In
Payme MCP Server

Payme MCP Server

by sirliboyev-uz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Verify Card

cards_verify

Verify a card by submitting the SMS verification code sent to the cardholder. Required after creating a card token.

Instructions

Verify a card using the SMS code sent to the cardholder. Must be called after cards_create. Example: cards_verify({ token: '630e5e...', code: '666666' })

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": {
      "token": "<token>",
      "code": "<code>"
    },
    "name": "cards_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSMS verification code
tokenYesCard token from cards_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, and description fails to disclose behavioral traits like idempotency, error handling, or rate limits. Only mentions verifying with SMS, leaving agent uninformed about important behavior.

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 sentences plus an example, front-loaded with purpose, no wasted words. Very concise and well-structured.

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?

Simple tool with 2 parameters, but missing output description (e.g., what a successful verification returns). Precondition is stated, but completeness is average.

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 covers 100% of parameters with descriptions. The description adds a concrete example but no additional semantic meaning beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (verify a card using SMS code) and distinguishes from siblings by specifying it must be called after cards_create.

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?

Explicitly states 'Must be called after cards_create', providing a clear usage guidance of when to use. Does not mention when not to use or alternatives, but the precondition is strong.

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