Skip to main content
Glama

Buscar proveedores en Nordelta

buscar_proveedores
Read-only

Busca proveedores de servicios recomendados por vecinos de Nordelta (Tigre, Buenos Aires). Acepta lo que pediría una persona: 'plomero', 'dermatóloga', 'clases de inglés', 'service de lavarropas', 'paseador de perros'. Devuelve nombre, rubro, teléfono, WhatsApp, descripción y link a la ficha.

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": "buscar_proveedores"
  }
}

Input Schema

NameRequiredDescriptionDefault
rubroNoOpcional: slug de rubro de listar_rubros (ej. 'plomeros') para traer todos los de ese rubro.
limiteNoMáximo de resultados (default 10).
consultaNoQué se busca, en español. Ej: 'gasista matriculado', 'técnico de aire acondicionado'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds that results are neighbor-recommended providers in a specific local area. It also enumerates returned fields (name, rubro, phone, WhatsApp, description, profile link), though it does not discuss result ordering or pagination.

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 two front-loaded sentences with no filler. The first defines the scope and query style, and the second lists the return fields.

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?

For a simple read-only search tool with three fully documented optional parameters and no output schema, the description supplies purpose, query style, and return fields. The main remaining gap is that it does not explicitly relate this tool to the sibling tools listar_rubros and ver_proveedor.

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 description coverage is 100%, so rubro, limite, and consulta are already fully documented in the schema. The description's examples add some flavor to the consulta parameter but do not add new semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it searches for recommended service providers in Nordelta (Tigre, Buenos Aires). It is clear, but it does not explicitly distinguish itself from the sibling tools listar_rubros and ver_proveedor.

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?

The description gives clear usage context by saying it accepts natural person-style queries such as 'plomero' or 'clases de inglés'. It does not provide explicit when-not guidance or name alternatives, but the intended query style is clear.

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