Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Worldwide advanced company data

get_company_WW_advanced
Read-onlyIdempotent

Retrieve detailed company information worldwide using a VAT or registration number and country code to verify businesses and access official data.

Instructions

Returns advanced company information for a company worldwide. Args: vatCode: VAT code or company registration number country_code: Two-letter country code of the country

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

Input Schema

NameRequiredDescriptionDefault
vatCodeYes
country_codeYes

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 read-only, idempotent and closed-world behavior, so the description need not repeat safety traits. It adds nothing about what happens when the VAT code is not found, whether the call consumes credits, or how large/complete the "advanced" dataset is, which matters for a lookup that may return empty results.

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 short, front-loaded sentences with no padding; the purpose statement comes first and the arguments follow. The "Args:" block is serviceable if slightly raw, but nothing is wasted.

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?

For a two-parameter read tool with no output schema, the description should at least characterize the returned data or the difference from the start/top tiers. It states none of that, so an agent must call it blind to discover what the response contains.

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 0%, so the description carries the parameter burden and does clarify that vatCode may be either a VAT code or a company registration number, and that country_code is a two-letter code. It gives no format examples, no case/whitespace expectations, and no indication of what happens with mismatched VAT code and country.

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?

Names a specific verb and resource ("Returns advanced company information") plus a scope ("worldwide"), so the agent knows it is a lookup tool. It does not distinguish itself from the tier siblings such as get_company_WW_start, get_company_WW_top or get_company_EU_advanced, leaving what "advanced" adds implicit.

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 prefer this over the other WW variants or over the country-specific tools, and no mention of prerequisites such as a valid VAT number being required. Usage is only inferable from the name.

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