Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

European/Worldwide basic company data

get_company_EU_start
Read-onlyIdempotent

Retrieve basic company details—name, VAT code, address, and activity status—by providing a VAT or registration number and two-letter country code.

Instructions

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

Returns companyName, vatCode, address, activityStatus, and other basic details.

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_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
vatCodeYesVAT code or company registration number.
country_codeYesTwo-letter country code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the safety profile is covered. The description adds value by naming the returned fields (companyName, vatCode, address, activityStatus), but says nothing about behavior on missing/invalid companies, coverage limits of 'basic', or response shape.

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?

Two short sentences, the purpose is front-loaded, and the return-field list is informative rather than padded. The closing 'and other basic details' is slightly vague but does not waste space.

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, listing the key returned fields is genuinely useful, and both required parameters are documented in the schema. What remains missing is the relationship to the many sibling company endpoints (basic vs advanced vs country-specific vs search), which matters given how dense this tool family is.

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%, so both vatCode and country_code are already documented, and the description only echoes 'specified country' without adding format, accepted-country, or registration-number nuance. Baseline 3 applies when the schema carries the semantics.

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

Purpose4/5

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

The description states a specific verb and resource ('Returns basic company information') scoped to 'the specified country', which matches the name's EU/worldwide basic-data framing. It does not, however, distinguish this from siblings such as get_company_EU_advanced or get_company_WW_start, so the agent must infer the 'basic vs advanced' boundary from names alone.

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

Usage Guidelines3/5

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

Usage is only implied: a VAT code plus country code yields a basic profile, which suggests this is the lightweight lookup. There is no explicit statement of when to prefer this over the advanced/full/search variants or what to do if the company is not found.

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