Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Start worldwide companies data from VAT or company number

get_company_WW_top
Read-onlyIdempotent

Retrieve worldwide company data by VAT or tax code and country code, including identity, address, contacts, classifications, and key balance sheet highlights.

Instructions

Returns worldwide top company data.

Includes company name, native company name, company size, address, GPS, activity status, incorporation date, contacts, classifications, and key balance sheet highlights.

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": {
      "vat_or_taxCode": "<vat_or_taxCode>",
      "country_code": "<country_code>"
    },
    "name": "get_company_WW_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYescountry code of the company
vat_or_taxCodeYesvatCode or taxCode of a company

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 disclosing the full field set returned, which tells the agent what data quality to expect, but says nothing about lookup failure behavior (unknown VAT), latency, or rate limits.

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

Conciseness4/5

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

Two sentences, front-loaded with the core purpose, followed by a compact enumeration of returned fields. The field list is long but each item is informative; no filler or redundancy.

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

Completeness4/5

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

With no output schema, the field enumeration effectively documents the return shape, which is the most important gap to close for a lookup tool. What remains missing is the distinction between this tier and the start/advanced siblings, which matters given how many similarly named tools exist.

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 country_code and vat_or_taxCode are already documented in the schema. The description adds no format hints (e.g. whether the VAT number should include the country prefix or which countries are supported), so the baseline of 3 applies.

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?

States a clear verb and resource ("Returns worldwide top company data") and enumerates the fields returned, so the agent knows exactly what payload to expect. It does not differentiate the "top" tier from sibling tiers such as get_company_WW_start or get_company_WW_advanced, leaving the tier semantics unexplained.

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 guidance on when to choose this over the sibling worldwide company tools, and no mention of prerequisites such as needing a valid VAT number or supported country coverage. The only usage signal is implicit in the title, which is not part of the description.

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