Skip to main content
Glama

AgentPay (Russia)

by io.github.zapnikita95

update_preference

Update stored preferences for a category after the user states a lasting rule («всегда 2.5%», «не покупай Whiskas», «размер 50», «цель сушка», «вес 80 кг») or after the onboarding phrase «Заполни предпочтения AgentPay». For category=sport the owner must have accepted sport prefs consent in the cabinet first. Do not use for one-off orders. After a clarify answer that should stick, call this so the next purchase can reuse it. Persist structured data only. Never invent fields the owner did not confirm. Sport prefs are for product picking, not medical advice. 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
dataYes
categoryYes
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).

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.5/5.0
Behavior5/5

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

With only default false annotations, the description carries the behavioral burden and does it well: it discloses persistence ('Persist structured data only'), confirmation constraints ('Never invent fields the owner did not confirm'), domain limits ('Sport prefs are for product picking, not medical advice'), and auth/retry behavior ('pass sessionId and retry. Never begin_agent_link again').

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 definition is long but front-loaded with purpose and triggers, and most imperatives carry real guardrail value. A few items ('Never web-search') feel tangential, and the auth/retry advice could be tighter, but overall the length is justified by the tool's pitfalls.

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?

Given the complexity (free-form data, consent prerequisite, auth retry), the description covers most operational needs: when to call, consent, structured-data-only, and session retry. The main gap is that data object shape and category enumerations are left to inference from examples; no output schema is needed for a persistence action.

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 only 33%, so the description must compensate. It does partly: examples like 'вес 80 кг' and 'Never invent fields' give semantic hints for data, and category=sport is called out. But it never defines the expected keys/values inside data or the full set of category values, leaving essential structure underspecified.

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?

Description starts with a specific verb+resource: 'Update stored preferences for a category' and immediately gives concrete trigger phrases ('всегда 2.5%', 'не покупай Whiskas'). It also draws a boundary from sibling write tools by saying 'Do not use for one-off orders', so the agent can distinguish it from purchase creation.

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?

States explicit when-to-use conditions: after a lasting rule or the onboarding phrase 'Заполни предпочтения AgentPay', and 'After a clarify answer that should stick'. It gives a when-not-to-use instruction ('Do not use for one-off orders') and a prerequisite for category=sport (owner must have accepted sport prefs consent).

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