Skip to main content
Glama
Sign In

Directorio Systema

by app.scalesystema
OverviewDiscussionsAdmin

Buscar por servicio o producto / Search by offering

buscar_por_servicio

ES: Busca negocios por lo que OFRECEN — un servicio, producto o clase concreta ("clases de zumba", "corte de caballero", "pupusas") — y devuelve cada negocio con los ítems que matchearon y su precio (o "cotizar"). Complementa buscar_negocios, que busca por nombre/categoría. / EN: Search businesses by what they OFFER — a specific service, product or class ("zumba classes", "men's haircut") — returning each business with its matched items and price (or "quote"). Complements buscar_negocios, which searches by name/category.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "consulta": "<consulta>"
    },
    "name": "buscar_por_servicio"
  }
}

Input Schema

NameRequiredDescriptionDefault
ciudadNoCiudad alrededor de la cual buscar / City to search around
consultaYesQué busca el usuario: "clases de zumba", "corte de caballero", "pupusas"… / What the user wants
ubicacionNoUbicación del USUARIO (no la del agente) / The USER's location (not the agent's)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ciudad / description
      Previous value: -"Filtrar por ciudad / Filter by city"New value: +"Ciudad alrededor de la cual buscar / City to search around"
    • addedInput schema / properties / ubicacion / properties / precisionMetros
      Added value: +{
+  "description": "Precisión de la ubicación en metros, si se conoce. Con más de 1000 m no se dan distancias / Location accuracy in meters, if known",
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It does disclose that the tool returns each business with its matched items and price-or-quote, which is useful. However, it does not describe result limits, no-match behavior, or any additional search semantics, leaving some behavioral uncertainty.

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 the core purpose and output, followed by the sibling distinction. The bilingual repetition increases length somewhat, but it is warranted and remains compact enough for an agent to scan quickly.

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?

The description is complete enough for a search tool: it states what to search by, what is returned, and names the main alternative. The schema covers all inputs, including the nested usuario location. It lacks details on result limits or edge cases, but these are not essential for basic invocation.

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?

The input schema has 100% description coverage, so the schema already documents all three parameters. The description's examples mostly restate what the consulta parameter description already provides, adding little new semantic information beyond reinforcement.

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 businesses by what they OFFER, with concrete examples. It also states the return shape (matched items with price or 'cotizar') and explicitly distinguishes this from the sibling buscar_negocios, which searches by name/category.

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 clearly identifies when the tool is appropriate: when the user is searching by a service, product, or class. It also names the relevant alternative, buscar_negocios, and contrasts it by name/category. It does not explicitly list exclusions for other sibling tools, so it is clear but not fully exhaustive.

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

All Directorio Systema toolsInspect
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