Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

European/Worldwide advanced company data

get_company_EU_advanced
Read-onlyIdempotent

Retrieve detailed European company data by VAT code and country, including financial highlights and extended registry information where available.

Instructions

Returns advanced company information for a company in the specified country.

Returns detailed company data including financial highlights or extended registry info where available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vatCode": "<vatCode>",
      "country_code": "<country_code>"
    },
    "name": "get_company_EU_advanced"
  }
}

Input Schema

NameRequiredDescriptionDefault
vatCodeYesVAT code or company registration number
country_codeYesTwo-letter country code (e.g., FR, DE, ES, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and repeatability are covered structurally. The description contributes the useful caveat 'where available', signalling partial or missing coverage for some companies, but says nothing about not-found behaviour, per-country coverage limits, or whether the call is billed/rate-limited.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the two sentences overlap heavily: 'advanced company information' is restated as 'detailed company data', with the only new content being the 'financial highlights or extended registry info' clause and the 'where available' hedge. The awkward line wrapping and redundancy cost it a point.

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

Completeness3/5

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

With no output schema, the description carries the burden of describing the return, which it does only loosely ('financial highlights or extended registry info'). Given the crowded tier/sibling landscape (EU/WW/IT × start/advanced/full/search), the definition never explains scope or country coverage, leaving the agent to infer it from the title.

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%, with both vatCode and country_code documented including a format example, so the schema does the heavy lifting. The description adds only 'in the specified country' and the notion that vatCode may be a registration number, which is already in the schema — a baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Returns advanced company information') and adds that results include 'financial highlights or extended registry info'. However, 'advanced' is undefined jargon and is not contrasted with the many sibling tiers in the catalog ('start', 'full', 'search', 'top', EU vs WW vs IT), so an agent cannot tell from the text why it would pick this over get_company_EU_start or get_company_WW_advanced.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites, and no named alternative or exclusion. The only usage signal is implicit in the parameter names, so the agent must guess how the 'advanced' tier relates to the 'start' and 'full' tiers.

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