Skip to main content
Glama

AgentPay (Russia)

by io.github.zapnikita95

poll_agent_link

Read-only

Poll AgentPay browser connect until the owner clicks Разрешить. Pass sessionId from begin_agent_link. No API key required. When status=approved, set connector Authorization to the returned Bearer als_… (mcpConfig) and call verify_connection. Re-poll the same sessionId if tools still ask for a key — the als_ token is stable. Never invent keys. Never ask the owner to paste ap_ from Агенты.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYessessionId from begin_agent_link

Schema Changelog

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

  1. Changed1 schema field changed
    • removedInput schema / properties / wait_seconds
      Removed value: -{
-  "description": "Optional 5–120. Server waits while owner clicks Разрешить. Use 90 after begin_agent_link.",
-  "type": "number"
-}
  2. Changed1 schema field changed
    • addedInput schema / properties / wait_seconds
      Added value: +{
+  "description": "Optional 5–120. Server waits while owner clicks Разрешить. Use 90 after begin_agent_link.",
+  "type": "number"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses the polling behavior, the stable token nature, and the follow-up action of setting Authorization and calling verify_connection. It also states that no API key is required, which is critical for the agent. Annotations are minimal (readOnlyHint) and the description adds substantial behavioral context without contradicting them.

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?

The description is a single paragraph that is information-dense but still efficient. Every sentence contributes actionable guidance, from the polling condition to the post-approval steps and warnings. It could be slightly more concise, but the structure is logical and front-loads the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description covers the full lifecycle: how to initiate, what to expect, how to proceed on approval, and common pitfalls. It is complete enough for an agent to execute the polling flow correctly without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers sessionId with a description, so the baseline is 3. The description reinforces its origin and emphasizes the stability for re-polling, adding semantic value about how to use the parameter. It does not fully compensate for any missing details, but the coverage is high and the added context is meaningful.

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 tool's purpose: polling AgentPay browser connect until the owner clicks 'Разрешить'. It specifies the resource and the condition for completion, and references the sibling begin_agent_link to set context. This differentiates it from related tools like verify_connection, which is called afterward.

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?

It gives explicit instructions: pass sessionId from begin_agent_link, re-poll the same sessionId if needed, and call verify_connection on approval. It also provides exclusions ('never invent keys', 'never ask owner to paste ap_'), which are clear negative guidance. This fully informs when and how to use the tool.

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