GYSM App and Store Builder

Find shops built on GYSM

find_stores

Read-onlyIdempotent

Search the online shops and businesses built on GYSM (products, appointments, services). Returns each live store's name, description and address. Read-only.

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": "find_stores"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	What the shopper wants, e.g. 'candles', 'haircut in Rome' (max 80 characters). Empty lists recent stores.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read-only' adds little. What the description does add is genuinely useful: it discloses the returned fields (name, description, address) and that only 'live' stores are included, which is a filtering behavior not visible in the annotations or schema (there is no output schema).

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?

Two short sentences, front-loaded with the action and domain, then the return shape. 'Read-only' is the only near-redundant clause since annotations already state it, but it costs little.

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 one-optional-parameter search with no output schema, the definition covers the domain, the result fields, and the live-only filter. Only the distinction from get_store and any result-count or pagination limits are unaddressed.

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% and the single optional parameter is fully documented there, including the max length and the empty-string behavior. The description adds no syntax or semantic detail beyond the schema, so the baseline 3 applies.

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?

The description pairs a specific verb ('Search') with a specific resource ('online shops and businesses built on GYSM') and enumerates the domain (products, appointments, services), which separates it from a single-store fetch like get_store. It stops short of naming any sibling explicitly, so an agent must infer the boundary with get_store or plan_online_store.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'Search' and the shopper-oriented example in the schema; there is no explicit statement of when to call this versus get_store (single shop) or plan_online_store (creating one). No prerequisites or exclusions are given.

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

All GYSM App and Store Builder 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?