Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Worldwide basic company data

get_company_WW_start
Read-onlyIdempotent

Retrieve basic company information for any country by supplying a VAT code or company registration number and a two-letter country code.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
vatCodeYes
country_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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 nothing behavioral beyond that — it does not clarify what 'basic' returns, whether a missing company yields an error or empty result, or any cost/rate considerations for a lookup service.

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?

The core purpose is front-loaded in a single sentence, followed by a compact Args block. The docstring-style parameter list slightly duplicates the schema, but it is short and earns its place given 0% schema coverage.

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 should convey what 'basic company information' actually contains, and it does not — field set, registration status, address scope are all unspecified. Combined with the absence of any tier comparison against the many sibling get_company_* tools, the definition is minimally adequate for invocation but leaves real ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 full burden, and it does so reasonably: vatCode is described as 'VAT code or company registration number' (clarifying an alias the schema does not), and country_code as a 'Two-letter country code' (clarifying the expected format). It stops short of examples or format details such as whether the country code is uppercase or whether VAT prefixes are accepted.

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 concrete verb and resource — 'Returns basic company information for a company worldwide' — which is clear enough to act on. It does not, however, distinguish 'basic' from the sibling tiers (get_company_WW_advanced, get_company_WW_top, get_company_EU_start), so an agent cannot tell from the text alone what 'basic' excludes.

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 or when-not-to-use guidance, and no mention of the advanced/top/EU/IT variants that clearly overlap. The only implicit selection signal is the required vatCode + country_code pair, which the agent has to infer.

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