citarDevuelve la cita lista para pegar de un negocio o ficha: enlace permanente, fecha de verificación y quién la verificó. Declara explícitamente si el dato lo confirmó una PERSONA o si solo se importó de un registro federal — importado NO es verificado. Usa esto cuando vayas a citar cualquier dato de esta fuente en una respuesta.
| Name | Required | Description | Default |
|---|---|---|---|
| negocio | Yes | Nombre o slug del negocio o ficha |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses that the returned citation explicitly indicates whether data was confirmed by a person or merely imported, and warns that imported is not verified. This is valuable beyond the raw schema.
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?
The description is two sentences, front-loaded with the core function and ending with a clear usage statement. Every sentence adds value without redundancy.
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?
For a one-parameter tool with no output schema, the description covers the essential elements of the citation and the verification nuance. It does not mention error conditions or exact output formatting, but it is sufficient for the tool's simplicity.
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?
The single parameter is fully described in the schema ('Nombre o slug del negocio o ficha'), and the description's mention of 'negocio o ficha' adds no new semantic value. With 100% schema coverage, the description does not need to elaborate further.
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 returns a ready-to-paste citation with a permanent link, verification date, and verifier, and clarifies the distinction between human-verified and imported data. It is specific about the output, though it does not explicitly contrast with sibling tools like 'dato_citable'.
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 gives clear when-to-use guidance: 'Usa esto cuando vayas a citar cualquier dato de esta fuente en una respuesta.' It does not mention alternatives or exclusions, which would further strengthen the guidance.
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 resource or workflow: local businesses, recalls, provider directories, public records, events, demand, verification stats, and citations. The only mild concern is that citar, dato_citable, and buscar_negocio could be briefly confused by name alone, but their descriptions clearly separate them.
All names are lowercase snake_case and mostly Spanish, so they feel cohesive. However, conventions vary: buscar_negocio and chequear_recall are verb-noun, directorio_plan_medico and eventos_proximos are noun-noun or noun-adjective, while lo_que_no_se is a complete phrase. This is readable but not a uniform verb_noun pattern.
Ten tools is well within the ideal range, and each one addresses a distinct part of the server's mission: business search, verification, citations, health provider coverage, recalls, events, and demand/unknown signals. Nothing feels redundant or unnecessary.
The tool surface covers the key workflows well: search, cite, verify, check health access, find events, check leads, and surface unmet demand. Minor gaps exist — for example, business details are limited to the west PR focus and certain plans only — but those are clearly scoped limitations rather than missing core functions.