Skip to main content
Glama

search_stores

Read-only

Find hardware stores in Spain by name, address, or location, or browse the full store catalog to locate shops for instant pick-up.

Instructions

Search or list stores in the Partle marketplace.

Use this when the user asks 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: Maximum results (1–50, default 20).

Returns: {"result": [Store, …]}. Each store includes id, name, address, country, lat/lon (when geocoded), homepage, and type. Pass id to search_products(store_id=…) to filter the product catalog by that store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
limitNo
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), describes rate limiting and no authentication, and explains the return format.

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?

Concise, well-structured, front-loaded with purpose, and every sentence adds value without redundancy.

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?

Lacking output schema, the description details the return structure and field list, plus a hint for downstream use with search_products.

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?

Despite 0% schema coverage, the description fully compensates by defining 'query' as free-text search and 'limit' with range and default.

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?

Clearly states the tool searches or lists stores, distinguishing it from product-led queries by explicitly referencing sibling tool 'search_products'.

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?

Provides explicit when-to-use (store-led questions) and when-not-to (product-led, use search_products), plus a browsing option with no query.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rubenayla/partle'

If you have feedback or need assistance with the MCP directory API, please join our Discord server