SAIKYO: pay from Russia

Search Saikyo Shop

search_saikyo_shop

Read-onlyIdempotent

Search Saikyo Shop digital goods paid in rubles: AI subscriptions, gift cards, game top-ups, Telegram Stars, software.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_saikyo_shop"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Language of returned links and titles (default en).
`query`	No	Product or brand, e.g. "ChatGPT Plus", "Steam".
`category`	No	Optional catalog category slug, e.g. "ai", "games", "subscriptions".

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / category / description

Added value: +"Optional catalog category slug, e.g. \"ai\", \"games\", \"subscriptions\"."

First observedSep 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world (openWorldHint=false), and the description is consistent with that by framing this as a fixed ruble-priced catalog. It adds no further behavior detail such as result limits, pagination, or ranking, so it is only marginally 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?

A single front-loaded sentence opening with the verb and resource, zero filler. The trailing enumeration is effectively a catalog scope statement, though it is long enough to read as a list rather than a crisp clause.

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?

With no output schema, the description should tell the agent what a result contains (names, prices, links, availability); it only implies titles/links via the lang parameter. Adequate for a read-only search but leaves the return shape to inference.

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% with all three parameters (lang, query, category) documented and an enum on lang, so the schema carries the parameter burden. The description adds scope context (ruble-priced digital goods) but no query syntax or category-slug guidance beyond the schema examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb+resource ("Search Saikyo Shop digital goods") with a concrete enumeration of the catalog's contents (AI subscriptions, gift cards, game top-ups, Telegram Stars, software) and the payment currency (rubles). It does not explicitly contrast itself with siblings, but the domain is obviously distinct from the exchange-rate/AML/payment-passport tools.

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

Usage Guidelines2/5

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

The description states what the tool searches but never says when to reach for it versus another tool, nor does it mention prerequisites or exclusions. An agent must infer usage purely from the domain wording.

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

All SAIKYO: pay from Russia tools Inspect

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

Need Help?