Skip to main content
Glama

AgentPay (Russia)

by io.github.zapnikita95

request_user_confirmation

Ask the human to confirm in AgentPay web or Telegram. Call when the user must approve a spend, freeze, or missing delivery data. Triggers: «спроси меня», «подтверди», HITL. Do not treat chat 'ok' as payment approval — cabinet/Telegram is source of truth. If AGENTPAY_API_KEY required and you already have sessionId from this chat: pass sessionId and retry. Never begin_agent_link again. Never ask the owner to edit connector settings or reconnect. Never web-search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNo
messageYes
sessionIdNoOptional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to open Authorization settings (Grok has none).
purchase_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to open Authorization settings (Grok has none).",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • removedInput schema / properties / sessionId
      Removed value: -{
-  "description": "Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to open Authorization settings (Grok has none).",
-  "type": "string"
-}
  3. Changed1 schema field changed
    • changedInput schema / properties / sessionId / description
      Previous value: -"Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to reconnect."New value: +"Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to open Authorization settings (Grok has none)."
  4. Changed1 schema field changed
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Optional. Agent-link sessionId from begin_agent_link / poll_agent_link. Pass on every tool when connector has no Authorization Bearer (Grok/ChatGPT/Claude). After status=approved this authenticates as als_<sessionId>. Never invent a sessionId. Never ask the owner to reconnect.",
+  "type": "string"
+}
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations provide no useful safety profile here, so the description carries the burden. It discloses important behavioral traits: external confirmation is required, the cabinet/Telegram is the source of truth, and a sessionId should be passed and retried if AGENTPAY_API_KEY is required. It does not describe the full side effect lifecycle or what happens after confirmation, but the behavioral context is substantial.

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?

The description is dense but every sentence adds operational value: what to do, when to do it, how to treat chat responses, how to handle sessionId, and what to never do. The most important action is front-loaded, and the guardrails are concise rather than padded.

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?

The tool has no output schema and no informative annotations, so the description must explain the full call context. It covers triggers, sessionId handling, and source-of-truth behavior. However, it does not describe what the response will be, how to interpret the confirmation outcome, or what to do when no sessionId is available and no API key is in place. Important edge-case context is missing.

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?

Schema description coverage is only 25%, so the description must compensate. It does clarify sessionId usage and the retry logic, but the meaning and expected format of the required 'message' parameter and the optional 'amount' parameter are left implicit. The description mentions approval contexts like spend and freeze, but does not explain how to populate the message or form the amount. This is insufficient for a low-coverage schema.

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: ask the human to confirm in AgentPay web or Telegram. It further specifies when it is appropriate: when the user must approve a spend, freeze, or missing delivery data, and even gives trigger phrases. This distinguishes it from the sibling tools, such as begin_agent_link, by explicitly warning not to call begin_agent_link again.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description gives explicit when-to-use conditions: approval of spend, freeze, or missing delivery data. It also provides when-not-to-use guidance: do not treat chat 'ok' as payment approval, never begin_agent_link again, never ask the owner to edit connector settings, and never web-search. This is strong routing and exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentPay (Russia) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Most tools target a distinct resource or action—get_* tools for financial/status lookups, search/get_product for catalog access, create_purchase for buying—but a few pairs share triggers. peek_stores and search_products can be triggered by the same phrases, and get_faq vs get_recovery_guide both address failure/error explanations, relying on the long descriptions to differentiate them.

Naming Consistency5/5

Tool names follow a consistent verb_noun snake_case pattern: get_* for read operations, create_/save_/update_/set_ for mutations, list_* for collection queries, and begin_/poll_/verify_ for the connection flow. No mixed casing or arbitrary verb variance is present.

Tool Count3/5

26 tools is on the heavy side, especially for a payment/shopping MCP server. While the domain is broad—auth, wallet, catalog, preferences, policies, purchases, recovery—some tools could be consolidated (e.g., peek_stores/search_products, get_faq/get_recovery_guide) without losing clarity.

Completeness4/5

The tool surface covers the full shopping/payment lifecycle: discovery, search, comparison, purchase, payment status, top-up, balance, limits, spending policy, address management, and connection recovery. Minor gaps exist—no explicit refund/cancel purchase tool and no preference deletion—but these can be worked around or are intentionally absent.

Resources