Skip to main content
Glama

AgentPay

by io.github.zapnikita95
OverviewDiscussionsAdmin

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». Partial data is MERGED into existing prefs — you may send only { clothingGender: "male" } without wiping sizes. For apparel gender use data.clothingGender = male|female|unisex|any. Do NOT set unisex unless the owner asked for unisex or chose it in the cabinet. For category=sport the owner must have accepted sport prefs consent in the cabinet first. Do not use for one-off gift 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.

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

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

Annotations only say the operation is not read-only and not destructive, but the description adds critical behavioral detail: partial data is merged, unisex must not be set unless explicitly asked, sport prefs need prior consent, structured data must be persisted, and fields must not be invented. It also explains sessionId retry behavior, going well beyond the annotations.

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 front-loaded with the core purpose and merge semantics up front, and most sentences carry operational value. Some trailing instructions like 'Never web-search' and 'Never ask the owner to edit connector settings' feel like broader platform rules rather than tool-specific guidance, adding slight bloat.

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 sparse schema and absent output schema, the description does a strong job covering merge semantics, allowed gender values, consent requirements, auth handling, and exclusions. The main missing piece is a complete list of valid category values and any expected response behavior, but the tool is still callable correctly with the provided guidance.

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?

Schema documentation only covers sessionId; category and data are minimally typed. The description compensates with concrete semantics like data.clothingGender = male|female|unisex|any, merge behavior, and category-specific consent for sport. However, it does not enumerate all valid category values or fully define the free-form data object, so a small gap remains.

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 names a clear action and resource: 'Update stored preferences for a category' after a specific trigger. It distinguishes itself from read-only and one-off purchase tools by saying 'Do not use for one-off gift orders.' No tautology; the purpose is explicit and actionable.

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 triggers: lasting user rules, the onboarding phrase, and sticky clarify answers. It also gives when-not-to-use guidance: one-off gift orders. Additional conditions like sport consent and specific rules for unisex make the usage context unambiguous.

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

All AgentPay toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources