Skip to main content
Glama

company_officers

Read-only

Retrieve a company's current and former officers, including appointment and resignation dates, from national registers using the country and registration number.

Instructions

List a company's officers (directors, secretaries, board members) from its national register, current and former, with appointment and resignation dates where the register publishes them.

    Needs the registration number (get it from company_lookup). For
    officers together with the register check, call company_lookup with
    include=["officers"] instead: one call, one price.

    Price: EUR 0.01 only when the register holds the company (free
    lookups first); NOT_FOUND costs nothing.
    Countries: GB, CZ, SK, NO, FR (GB, CZ, SK also list former officers).

    Args:
        country: ISO 3166-1 alpha-2 code, e.g. "GB"
        registration_number: The register's company number, e.g. "00445790"
    

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": {
      "country": "<country>",
      "registration_number": "<registration_number>"
    },
    "name": "company_officers"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYes
registration_numberYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/non-destructive annotations, it discloses pricing (EUR 0.01, free lookups first), that NOT_FOUND is free, country coverage (GB, CZ, SK, NO, FR), and which countries include former officers. That is exactly the kind of cost and coverage context annotations cannot express.

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?

Front-loaded with purpose, then prerequisites, cost, and coverage, with a clean Args block at the end. Slightly dense with parentheticals, but nearly every sentence carries decision-relevant information rather than restating the name.

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

Completeness5/5

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

Covers the full path to a correct call: how to get the required input, cost and failure behavior, which countries are supported, and when a sibling call is superior. An output schema exists, so return values need not be described.

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 coverage is 0%, so the description carries the load: it defines country as ISO 3166-1 alpha-2 with "GB" as an example and registration_number as the register's company number with "00445790" as an example, plus where to obtain it. It stops short of per-country number formats, which is a small residual gap.

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

Purpose5/5

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

States a specific verb and resource ("List a company's officers") and immediately scopes it: directors, secretaries, board members, current and former, with appointment/resignation dates. It also distinguishes itself from the sibling by naming company_lookup with include=["officers"] as the combined alternative.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite (registration number, obtained from company_lookup) and an explicit alternative path when the agent also needs the register check ("one call, one price"). The condition selecting each path is spelled out rather than inferred.

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