Papyras Coupons

Search stores

search_stores

Read-onlyIdempotent

Search the stores that currently have live offers, by name or domain. Use it when the store name is unclear or to compare country versions of a store.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_stores"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	Yes	Store name or part of it, or a domain.
`country`	No	Optional ISO country code (US, UK, DE, …) to prefer stores that serve that country. Worldwide stores are always included.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/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 behavior, so the safety profile is covered. The description adds one useful behavioral fact, that results are restricted to stores with currently live offers, but says nothing about result ordering, pagination, or what happens when the limit is hit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, with the core scope stated first and the usage hint second. Nothing is redundant with the title or restated unnecessarily.

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?

For a simple read-only search with rich annotations, a fully enumerated schema and no output schema, the definition is nearly sufficient. Minor gaps are how results are ranked and what a returned store record contains, which an agent might otherwise have to discover by calling it.

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 67%; query and country are documented in the schema, and the description reinforces them ("by name or domain", "compare country versions"). The limit parameter carries no description in either place, so the description does not fully compensate for the remaining gap.

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?

"Search the stores that currently have live offers, by name or domain" is a specific verb+resource with a meaningful scope qualifier (only stores with live offers). It is clearly a discovery/lookup tool rather than an offer-fetching tool, though it never names a sibling such as get_store_offers to sharpen the distinction.

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

Usage Guidelines4/5

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

It gives a concrete usage trigger: "Use it when the store name is unclear or to compare country versions of a store." That is clear when-to-use context, but it offers no when-not guidance and no explicit alternative to call when the store identifier is already known.

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

All Papyras Coupons 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?