Skip to main content
Glama
Sign In

Growkik Directorios

by com.growkik
OverviewDiscussionsAdmin

Buscar empresas cerca de un lugar

buscar_cerca
Read-onlyIdempotent

Busca empresas dentro de un radio (km) alrededor de un municipio, una empresa, un parque industrial o unas coordenadas, ordenadas de la más cercana a la más lejana, con la distancia en km. Acepta los mismos filtros que buscar_empresas (texto, directorio, categoría, tamaño, sitio web y los de datos adicionales). El centro de un municipio es la mediana de las coordenadas de sus empresas. No devuelve teléfonos ni correos.

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_cerca"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoCentro: latitud (con lng).
lngNoCentro: longitud (con lat).
textoNoPalabras a buscar, igual que en buscar_empresas.
estadoNoEstado del municipio, para distinguir municipios con el mismo nombre.
paginaNoPágina, desde 1.
radio_kmNoRadio en km, 20 por omisión, máximo 100.
categoriaNoSlug o nombre de categoría (ver listar_directorios), p. ej. naves-industriales, automotriz-aeroespacial, agencias-aduanales.
municipioNoCentro: municipio o ciudad, p. ej. Apodaca, Celaya, Silao.
alta_desdeNoSolo establecimientos que entraron al DENUE desde ese año o mes, 'AAAA' o 'AAAA-MM'. Es la fecha de alta en el DENUE, no la de fundación.
directorioNoconstruccion, industria, inmobiliarias o transporte. Omitir busca en los cuatro.
por_paginaNoResultados por página, máximo 25 (10 por omisión).
con_contactoNoSolo empresas que tienen teléfono o correo en la descarga de pago.
con_sitio_webNoSolo empresas con sitio web.
tamano_minimoNoTamaño mínimo por plantilla DENUE: micro (0-5), pequena (6-30), mediana (31-100), grande (101+).
cerca_de_parqueNoCentro: un parque industrial, por su id de buscar_parques_industriales.
cerca_de_empresaNoCentro: una empresa, por su id 'directorio:slug' o la URL de su ficha.
capital_extranjeroNoSolo empresas con inversión extranjera registrada en el RNIE de la Secretaría de Economía.
proveedor_gobiernoNoSolo empresas con contratos federales desde 2024 en ComprasMX (coincidencia por razón social).
certificado_ambientalNoSolo empresas con un certificado ambiental vigente de PROFEPA (Industria Limpia o Calidad Ambiental).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: deterministic distance ordering, distance returned in km, how a municipio center is computed (median of its companies' coordinates), and the important output limitation that no phones or emails come back despite the con_contacto filter.

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?

Four sentences, front-loaded with the core behavior, and each one carries information: scope, filter parity, centroid rule, output limitation. The parenthetical enumeration of filters slightly duplicates the schema but serves as a quick pointer to buscar_empresas.

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 19 optional parameters, the description covers the essentials: what gets returned (ordered results with km distance), what does not (contacts), and the center-selection options. The main residual gap is that it never states whether exactly one center parameter must be supplied or what happens if several are given.

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% across 19 parameters, so the baseline is 3 and the schema does most of the work. The description contributes the notion of a single center drawn from lat/lng, municipio, parque or empresa, and clarifies the centroid semantics of municipio, but adds nothing on the many boolean data filters or their combination rules.

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?

Names a specific verb and resource (buscar empresas) plus the defining scope: a radius in km around one of four center types, results ordered nearest-first with distance in km. That geo-radius scope is exactly what separates it from the sibling buscar_empresas, so an agent can pick between them without opening either 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?

Implies clearly when to use it (proximity queries around a place) and tells the agent that the same filters as buscar_empresas apply, which routes filter knowledge to the sibling. It stops short of an explicit exclusion such as 'use buscar_empresas when you do not need proximity or distance ordering.'

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

All Growkik Directorios 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