Busca personas (directores, socios, gerentes, síndicos, apoderados de empresas argentinas) por nombre. Devuelve CUIT, nombre y cantidad de empresas vinculadas de cada una. Cuesta 1 crédito por página.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | nombre a buscar, mínimo 3 caracteres | |
| pagina | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It describes the search scope, returned fields, and cost per page. However, it does not mention pagination behavior or error conditions, which are important for a search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core purpose, followed by constraints and cost. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and partial schema coverage, the description provides key details: search scope, returned data, and cost per page. It is adequate for a straightforward search tool, though pagination behavior could be clearer.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50% (only 'q' parameter described). The description adds context about searching by name but does not elaborate on the 'pagina' parameter beyond implying pagination via cost per page. The description adds some value but does not fully compensate for the missing schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool searches for people (directors, partners, managers, etc.) by name and lists returned fields (CUIT, name, number of linked companies). It clearly distinguishes from sibling tools like 'buscar_empresas'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains what the tool does and mentions the cost per page, but does not provide explicit when-to-use or when-not-to-use guidance, nor alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct entity or action: searches for people, companies, importers, and tenders are clearly separated, as are company and person detailed profiles, credit balance, and autocomplete. The two overlapping-looking tools (buscar_empresas and sugerencias) differ in purpose: full search vs. lightweight autocomplete, so no real ambiguity exists.
Tool names follow a clear pattern: buscares use verb_noun, fichas use noun_noun, and saldo_creditos/sugerencias are standalone nouns. This is mostly consistent and predictable, with minor deviation from a strict verb_noun pattern.
With 8 tools, the server is well-scoped for its purpose of retrieving Argentine business data. It covers multiple search domains, detailed profiles, account management, and autocomplete without excessive fragmentation or unnecessary tools.
The core domain is well covered: search for companies, people, importers, and tenders, plus detailed profiles for companies and people. A minor gap is the lack of detail views for individual importers or tenders beyond search results, but agents can typically work around this with the existing search capabilities.
