Skip to main content
Glama
Sign In

Growkik Directorios

by com.growkik
OverviewDiscussionsAdmin

Buscar empresas

buscar_empresas
Read-onlyIdempotent

Busca empresas en los directorios por texto (nombre, razón social, actividad, productos), directorio, categoría, estado, municipio y tamaño. Devuelve hasta 25 por página con nombre, actividad, ubicación, tamaño, sitio web, si tiene teléfono/correo en la descarga de pago, y el enlace a su ficha. 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_empresas"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoNoPalabras a buscar: nombre de la empresa, actividad o producto (p. ej. 'acero estructural', 'Bimbo', 'refrigerada').
estadoNoEstado de México (nombre, slug o abreviatura como CDMX, NL, Edomex). Omitir = todo el país.
paginaNoPágina, desde 1.
categoriaNoSlug o nombre de categoría (ver listar_directorios), p. ej. naves-industriales, automotriz-aeroespacial, agencias-aduanales.
municipioNoMunicipio o ciudad, p. ej. Monterrey, Apodaca, Tijuana.
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+).
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. Changed4 schema fields changed
    • addedInput schema / properties / alta_desde
      Added value: +{
+  "description": "Solo 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.",
+  "maxLength": 7,
+  "type": "string"
+}
    • addedInput schema / properties / capital_extranjero
      Added value: +{
+  "description": "Solo empresas con inversión extranjera registrada en el RNIE de la Secretaría de Economía.",
+  "type": "boolean"
+}
    • addedInput schema / properties / certificado_ambiental
      Added value: +{
+  "description": "Solo empresas con un certificado ambiental vigente de PROFEPA (Industria Limpia o Calidad Ambiental).",
+  "type": "boolean"
+}
    • addedInput schema / properties / proveedor_gobierno
      Added value: +{
+  "description": "Solo empresas con contratos federales desde 2024 en ComprasMX (coincidencia por razón social).",
+  "type": "boolean"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: a hard cap of 25 results per page, the exact fields returned, and the important limitation that phones and emails are never returned and only appear in the paid download. It does not mention pagination limits (pagina max 200) or total-count behavior, which would complete the picture.

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?

Three sentences, each earning its place: search scope first, then return payload, then the negative constraint. No filler and the most decision-relevant facts are front-loaded.

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 14-parameter, zero-required search tool with no output schema, the description does the necessary work by describing the result shape and the no-contact limitation. Remaining gaps are minor: no mention of the page ceiling or of the sibling tool for aggregate counts.

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 every one of the 14 parameters is already documented with examples and enum values. The description restates the high-level filter categories but adds no syntax or format detail beyond the schema; baseline 3 applies when the schema carries the semantic load.

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?

States a specific verb and resource ('Busca empresas en los directorios') and enumerates the searchable dimensions (texto, directorio, categoría, estado, municipio, tamaño), which lets an agent recognize a filtered company search. It stops short of naming a sibling such as contar_empresas or buscar_cerca to differentiate itself explicitly, so it is clear but not fully disambiguated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the enumerated filters make it obvious this is the tool for filtered company lookup, and 'No devuelve teléfonos ni correos' hints that contact retrieval belongs elsewhere. There is no explicit statement of when to prefer contar_empresas (counting), buscar_cerca (proximity) or obtener_contactos (contact details).

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