empresas

buscar_empresas

Read-only

Busca empresas argentinas por razón social y/o filtros combinables (forma legal, jurisdicción, ciudad, actividad, estado fiscal, rango de capital y sellos booleanos como importador/exportador/empleador/contratista) sobre un padrón de ~1,3M de empresas. Devuelve hasta 50 resultados por página con el total. Cuesta 1 crédito por página.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	búsqueda textual por razón social
`pep`	No	true = solo empresas con el sello "Vinculada a funcionario (PEP)"
`apoc`	No	true = solo empresas con el sello "En base APOC"
`ciudad`	No
`pagina`	No
`repsal`	No	true = solo empresas con el sello "Sanciones laborales (REPSAL)"
`capital`	No	rango de capital del último balance: lt-1m \| 1m-10m \| 10m-100m \| gt-100m
`actividad`	No	código de actividad AFIP de hasta 6 dígitos (620100, 011211)
`empleador`	No	true = solo empresas con el sello "Empleadora"
`deuda_bcra`	No	true = solo empresas con el sello "Con deuda BCRA"
`exportador`	No	true = solo empresas con el sello "Exportadora"
`importador`	No	true = solo empresas con el sello "Importadora"
`sancionada`	No	true = solo empresas con el sello "Sancionada (UIF/CNV/BCRA)"
`contratista`	No	true = solo empresas con el sello "Contratista del Estado"
`forma_legal`	No	sa, srl, sas, cooperativa, fundacion…
`jurisdiccion`	No	provincia o 'Ciudad Autónoma de Buenos Aires'
`estado_fiscal`	No	activa \| inactiva \| baja \| suspendida \| unknown
`cheque_rechazado`	No	true = solo empresas con el sello "Con cheques rechazados"
`concurso_quiebra`	No	true = solo empresas con el sello "En concurso o quiebra"

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedInput schema / properties / actividad / description

Previous value: -"código de actividad AFIP"New value: +"código de actividad AFIP de hasta 6 dígitos (620100, 011211)"

Changed13 schema fields changedAug 17, 2026

addedInput schema / properties / apoc

Added value: +{
+  "description": "true = solo empresas con el sello \"En base APOC\"",
+  "type": "boolean"
+}

addedInput schema / properties / capital

Added value: +{
+  "description": "rango de capital del último balance: lt-1m | 1m-10m | 10m-100m | gt-100m",
+  "type": "string"
+}

addedInput schema / properties / cheque_rechazado

Added value: +{
+  "description": "true = solo empresas con el sello \"Con cheques rechazados\"",
+  "type": "boolean"
+}

addedInput schema / properties / concurso_quiebra

Added value: +{
+  "description": "true = solo empresas con el sello \"En concurso o quiebra\"",
+  "type": "boolean"
+}

addedInput schema / properties / contratista

Added value: +{
+  "description": "true = solo empresas con el sello \"Contratista del Estado\"",
+  "type": "boolean"
+}

addedInput schema / properties / deuda_bcra

Added value: +{
+  "description": "true = solo empresas con el sello \"Con deuda BCRA\"",
+  "type": "boolean"
+}

addedInput schema / properties / empleador

Added value: +{
+  "description": "true = solo empresas con el sello \"Empleadora\"",
+  "type": "boolean"
+}

addedInput schema / properties / estado_fiscal / description

Added value: +"activa | inactiva | baja | suspendida | unknown"

addedInput schema / properties / exportador

Added value: +{
+  "description": "true = solo empresas con el sello \"Exportadora\"",
+  "type": "boolean"
+}

addedInput schema / properties / importador

Added value: +{
+  "description": "true = solo empresas con el sello \"Importadora\"",
+  "type": "boolean"
+}

addedInput schema / properties / pep

Added value: +{
+  "description": "true = solo empresas con el sello \"Vinculada a funcionario (PEP)\"",
+  "type": "boolean"
+}

addedInput schema / properties / repsal

Added value: +{
+  "description": "true = solo empresas con el sello \"Sanciones laborales (REPSAL)\"",
+  "type": "boolean"
+}

addedInput schema / properties / sancionada

Added value: +{
+  "description": "true = solo empresas con el sello \"Sancionada (UIF/CNV/BCRA)\"",
+  "type": "boolean"
+}

First observedJul 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses concrete behavioral details: up to 50 results per page with a total, a 1-credit-per-page cost, and the underlying dataset size. These details are not present in the annotations and help the agent plan pagination and credit usage.

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 three sentences with no filler: purpose and filtering capacity, then result pagination with total, then cost. The most decision-relevant information is front-loaded and every sentence carries operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter, read-only search tool with no output schema, the description supplies the essential invocation context: what is searched, the filter families, result size, total count, and credit cost. Combined with the 89% schema coverage, an agent has enough to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (89%), so the schema already documents most parameters. The description adds the important interaction semantic that filters are combinable ('filtros combinables') and illustrates the boolean stamp families, which goes slightly beyond the individual parameter descriptions without restating schema values.

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 begins with a specific verb and resource ('Busca empresas argentinas') and defines the scope over a 1.3M-company registry with combinable filters. It also distinguishes this general company search from narrower siblings such as buscar_importadores by framing importador/exportador as optional boolean stamps rather than the tool's sole focus.

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 clearly states the use case: find Argentine companies by corporate name and/or a combination of filters, with pagination and cost. It does not explicitly name alternative tools or provide when-not-to-use exclusions, so it provides clear context but not full routing.

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

All empresas tools Inspect

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

Need Help?