Skip to main content
Glama

search_products

Read-only

Search Partle's catalog of hardware and tools by name, description, or semantic query. Filter by price, store, and tags to locate products in physical stores.

Instructions

Search Partle's product catalog by name or description.

Use this when the user asks to find a specific product or browse products matching a query. Prefer this over search_stores when the intent is product-led ("find a drill") rather than store-led ("what stores are near Madrid"). Use get_product afterwards if the user wants full details for one specific result.

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

Args: query: Free-text search term (e.g. "wireless headphones", "cerrojo FAC", "drill bit"). Required even in semantic mode. min_price: Lower bound on price in EUR. Omit for no lower bound. max_price: Upper bound on price in EUR. Omit for no upper bound. tags: Comma-separated tag filter (e.g. "electronics,bluetooth"). Tags are AND-ed together. store_id: Restrict results to a single store. Use the integer id field from search_stores results. sort_by: One of price_desc, name_asc, newest, oldest. Omit to use the default search-relevance ranking. semantic: When True, runs a vector / cross-language search. Set this when the user's query may not match the listing language — e.g. "drill" in English will also surface "taladro" (Spanish) and "Bohrmaschine" (German). Pure-English catalogs benefit less. limit: Maximum results (1–100, default 20). Larger limits are slower and may exceed the rate budget faster. offset: Skip this many results before returning. Use for pagination (offset += limit on each follow-up call).

Returns: {"result": [Product, …]}. Each product includes id, name, price, currency, url, description, store (id / name / country), images, tags, and a canonical partle_url. Always share partle_url with the user so they can view the listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
min_priceNo
max_priceNo
tagsNo
store_idNo
sort_byNo
semanticNo
limitNo
offsetNo
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description adds: 'No authentication. Rate-limited to 100 requests/hour per IP.' It explains semantic search behavior and default sorting. No contradictions with annotations. This fully discloses behavioral traits.

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?

The description is front-loaded with purpose and usage guidelines, then param details neatly listed. Every sentence adds value, but the param section is somewhat lengthy. Still, it is well-structured for readability. Slightly verbose but not wasteful, so a 4 is appropriate.

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?

Given the complexity (9 parameters, no output schema), the description fully covers parameter semantics, return format (including fields like partle_url), pagination hints, rate limits, and authentication. It tells the agent to share partle_url with the user. This is complete and thorough.

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 0% schema description coverage, the description provides extensive and meaningful parameter explanations for all 9 parameters, including valid values, defaults, and usage notes. This compensates entirely for the lack of schema descriptions, meriting a 5.

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?

Description clearly states 'Search Partle's product catalog by name or description' with a specific verb and resource. It distinguishes from sibling search_stores by explaining product-led vs store-led usage, and points to get_product for follow-up. This meets the criteria for a 5.

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 (product-led queries) and when to use the alternative search_stores (store-led). Also advises using get_product for full details. This provides clear context and exclusions, earning a 5.

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