Partle

search_stores

Read-only

Search or list stores in the Partle marketplace.

Use for store-led questions ("what hardware shops are in Madrid?") rather
than product-led ones (use `search_products` for that). Pass no query to
browse the whole catalog.

Read-only. No authentication. Rate-limited to 100 requests/hour per IP.

Args:
    query: Free-text search over store name and address. Omit to list
        all stores in default order.
    limit: Max results (1–50, default 20).

Returns:
    A list of stores with `id`, `name`, `address`, `lat`/`lon` (when
    geocoded), `homepage`, `type`, and `product_count` (active listings
    in the store — useful for competitive-landscape sizing without a
    separate `search_products` round-trip). Pass `id` to
    `search_products(store_id=…)` to filter the product catalog by that
    store.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedFeb 27, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description adds critical operational details: 'Read-only. No authentication. Rate-limited to 100 requests/hour per IP.' It also discloses data nuances like 'lat/lon (when geocoded)' and the utility of product_count. These are genuine behavioral traits not captured by structured fields.

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?

The description is well-structured with clear sections (intro, usage guidance, behavioral notes, Args, Returns). Every sentence serves a purpose, avoiding fluff. It is detailed yet concise, fitting the multi-faceted nature of the tool without being bloated.

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?

The description covers all necessary aspects: purpose, when to use (vs search_products), parameter semantics, return fields (including optional geocoding), rate limits, and even an integration hint (pass id to search_products). Despite having an output schema, the description enriches it with use-case guidance, making it complete for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 0%, the description fully compensates. It explains that `query` is free-text over store name and address, and that omitting it lists all stores in default order. It also clarifies that `limit` accepts 1–50 with a default of 20, adding range and meaning beyond the bare schema.

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 opens with 'Search or list stores in the Partle marketplace', using a specific verb and resource. It clearly distinguishes itself from product-led search by pointing to `search_products` for that use case, which separates it from sibling tools.

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?

Explicitly states when to use this tool: 'Use for store-led questions... rather than product-led ones (use `search_products` for that)'. It also explains how to browse the full catalog by omitting the query, and provides meaningful context about rate limiting and read-only behavior.

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

All Partle 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.