Skip to main content
Glama

Belgium company

run_be_companies
Read-onlyIdempotent

Get one company from the Belgium registry (KBO/BCE) by enterprise number or registry URL: name, status, start date, address, legal form, activities, directors, contact details and establishment units. 10 points per returned record.

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": {
      "company": "<company>"
    },
    "name": "run_be_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesEnterprise number or registry URL. e.g. 0202.239.951

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds two things beyond them: the concrete payload contents (directors, establishment units, contact details) and the cost model '10 points per returned record', which is real behavioral information an agent needs before calling.

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 sentences: the resource and identifier forms come first, the payload contents and cost follow. No filler, no restating of the tool name, nothing that could be cut without losing information.

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 (name, status, start date, address, legal form, activities, directors, contact, establishment units) does the job of telling the agent what comes back, and pricing is disclosed. Minor gap: no indication of behavior on not-found or invalid enterprise numbers, or of response latency for the open-world lookup.

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 coverage is 100% for the single parameter, and the schema already documents the accepted forms with an example ('0202.239.951'). The description restates the same two input forms without adding format rules, validation behavior, or what happens on an unmatched number, so the baseline 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 specific verb and resource ('Get one company from the Belgium registry (KBO/BCE)') and enumerates the returned fields, so the scope is unambiguous. It signals single-record lookup versus the numerous 'run_*_companies_search' siblings, but never names run_be_companies_search as the alternative, so the differentiation is implied rather than explicit.

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?

The phrase 'by enterprise number or registry URL' implies this is a direct-lookup tool for when you already have an identifier, which is useful usage context. However, there is no explicit when-to-use/when-not guidance and no mention of run_be_companies_search for the case where only a name is known.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources