Skip to main content
Glama

Products Search Nearby

products-search-nearby

Search for products available in nearby physical stores in Spain. Pass lat/lon, or a place name if you do not have coordinates. Returns stores ordered by usefulness (priced and in stock first), each with up to 3 matching products: price, availability, trust level, and distance. Queries work best in Spanish ("leche entera", "ibuprofeno 600"). If the result is empty, retry with a larger radius (e.g. 5000) or a more generic term. Fields that are unknown are omitted. When availability_status is unknown or unreachable, do NOT affirm availability — recommend the user confirms with the store directly.

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": "products-search-nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
placeNo
queryNo
radiusNo
trust_levelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose meaningful behavior: result ordering by usefulness (priced and in stock first), at most 3 products per store, unknown fields omitted, and an explicit caution not to affirm availability when the status is unknown or unreachable. It omits permission, rate-limit and latency characteristics, which keeps it short of a 5.

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 input form, then return shape, then recovery and safety advice, and every sentence carries actionable content. It is dense but not padded, though the availability caveat could be tightened.

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?

With no output schema and no annotations, the description still describes the return payload (price, availability, trust level, distance, ordered by usefulness) and the empty-result fallback. The only material gap for a six-parameter tool is the unexplained trust_level parameter.

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 0% across six parameters, so the description must compensate. It explains lat/lon vs place, query phrasing and the radius example value, but it never mentions trust_level or what values it accepts, leaving one parameter undocumented in both places.

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 names a specific verb and resource ('Search for products available in nearby physical stores in Spain'), which is distinct from the sibling retrieval tools products-get, stores-get and stores-search. An agent can tell that this is a geographic proximity product search without opening any schema.

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 concrete routing guidance for inputs ('Pass lat/lon, or a place name if you do not have coordinates') and a recovery strategy ('retry with a larger radius (e.g. 5000) or a more generic term'). It also advises Spanish queries for better recall. It never explicitly contrasts itself with products-get or stores-search, so the alternative-selection guidance is incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources