Skip to main content
Glama

Ozerki via AgentPay

by io.github.zapnikita95
OverviewDiscussionsAdmin

get_faq

Read-only

Look up AgentPay operational FAQ before guessing. Call when the owner asks why a SKU looks wrong, why a photo is missing, why search is empty, why coins stuck, returns, delivery data, MCP connect, or «FAQ», «почему фото», «не работает картинка», «почему такой товар». Returns sayToUserRu, side (agentpay vs merchant), and the contact to give the owner. Do not invent a reason. Do not hide whose side it is.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesOwner question or error phrase in Russian or English
storeIdNoOptional store UUID when the issue is about a shop

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
-}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, but the description adds valuable behavioral context: it returns sayToUserRu, side (agentpay vs merchant), and the contact to give the owner. It also instructs not to invent reasons and not to hide the side, which are behavioral rules beyond the annotations. No contradiction with 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 a bit verbose but every sentence carries meaning: the trigger list is extensive, the return content is specified, and the behavioral rules are included. It's front-loaded with the core purpose ('before guessing') and structured logically. Minor redundancy could be trimmed, but it's still efficient for the information density.

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?

With no output schema, the description compensates by specifying the exact return fields (sayToUserRu, side, contact). It also covers usage context and constraints. For a simple two-parameter tool, nothing essential is missing—an agent can call it correctly and interpret the response.

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 description coverage is 100%, so both 'q' and 'storeId' are already documented in the schema. The description adds no new parameter-level detail beyond what the schema provides; it just restates the trigger phrases for 'q'. This meets the baseline 3 but doesn't elevate it.

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: looking up AgentPay operational FAQ. It lists specific trigger scenarios (why SKU looks wrong, missing photo, empty search, etc.) and specifies the return content (sayToUserRu, side, contact). This distinguishes it from siblings like search_products or get_product, which have different roles.

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 explicitly says 'Call when the owner asks...' followed by a concrete list of triggers, including Russian phrases. It also gives exclusions: 'Do not invent a reason' and 'Do not hide whose side it is,' which are clear usage rules. Though it doesn't name alternative tools, the trigger list is specific enough to route an agent correctly.

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

All Ozerki via 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