get_showcaseCurated IBEX35 + EU entity examples. FREE — does not consume quota. Use to explore data depth.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Sample size (default 3, max 5) | |
| category | No | Subset to sample (default: all) |
| Name | Required | Description | Default |
|---|---|---|---|
| _meta | No | ||
| unlock | No | ||
| checkout | No | ||
| entities | No | ||
| upgrade_url | No | ||
| access_level | No | ||
| gated_fields | No | ||
| upgrade_hint | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful behavior beyond that: it explicitly says the operation is FREE and does not consume quota, and notes that results are curated rather than exhaustive. This is useful operational context for an agent deciding whether to invoke it.
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 short sentences communicate scope, cost behavior, and intended use with no filler. The most important qualifier, 'does not consume quota', is front-loaded. Every clause earns its place.
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?
This is a simple, optional-parameter, read-only sampling tool with a full output schema and complete parameter documentation. The description supplies the missing operational context—curated, free, quota-free, exploratory—so an agent has everything needed to invoke it correctly without additional inference.
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 description coverage is 100%, so the schema already documents limit and ategory well. The description's mention of 'IBEX35 + EU' loosely aligns with the category enum values but adds no new parameter information beyond what the schema provides. Baseline 3 is appropriate.
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 clearly identifies the tool as returning curated IBEX35 and EU entity examples, which distinguishes its purpose as a sampler/exploration tool. It lacks an explicit verb like 'returns' or 'retrieves', and it does not directly contrast with sibling tools, but the resource and intent are clear.
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 phrase 'Use to explore data depth' gives a clear intended context, and the quota note helps the agent know when cost is a concern. However, it does not explicitly state when to prefer this over alternatives such as search_entities or entity_lookup, nor does it provide exclusions.
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.
Most tools target distinct resources, but get_entia_home and get_entity_home_projection are near-duplicates representing the same Entia Home concept from slightly different technical angles. entity_lookup and get_full_dossier also overlap since entity_lookup already mentions returning the full paid dossier, and get_competitors is a specialized variant of search_entities.
The set mixes get_* names with bare action names like entity_lookup, search_entities, verify_vat, and professional_lookup, so there is no single consistent verb_noun pattern. The names are still readable and somewhat predictable, but the inconsistency is noticeable and get_entia_home vs get_entity_home_projection adds confusion.
Twelve tools is within a reasonable range for an entity-verification server, and most tools serve a distinct due-diligence purpose. However, a few tools are auxiliary or redundant: get_showcase and get_platform_stats are exploratory rather than core verification, and the two Entia Home retrieval tools could be consolidated.
The server covers the core verification lifecycle well: entity lookup by identifiers, flexible search, VAT validation, professional verification, competitor discovery, full dossiers, and risk auditing. Minor gaps exist, such as no direct way to fetch a raw single source like VIES or BORME independently and no entity relationship/ownership endpoint, but these are workable for typical KYB workflows.