Skip to main content
Glama

Search Officers

search_officers
Read-onlyIdempotent

Search company officers and directors by name. Returns officer name, position, company, start/end dates, and nationality. REQUIRES your own OpenCorporates API token via _apiKey, their public API is closed and keyless calls return 401. Example: search_officers({query:"Elon Musk", _apiKey:"..."})

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Elon Musk"
    },
    "name": "search_officers"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesOfficer name to search (e.g., "John Smith")
_apiKeyNoYour OpenCorporates API token (required, get one at https://opencorporates.com/api_accounts/new)

Output Schema

NameRequiredDescriptionDefault
queryYesThe search query used
totalYesTotal number of matching officers
officersYesList of matching officers
returnedYesNumber of officers returned in this response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Your OpenCorporates API token (required — get one at https://opencorporates.com/api_accounts/new)"New value: +"Your OpenCorporates API token (required, get one at https://opencorporates.com/api_accounts/new)"
  2. Changed1 schema field changed
    • addedInput schema / properties / _apiKey
      Added value: +{
      +  "description": "Your OpenCorporates API token (required — get one at https://opencorporates.com/api_accounts/new)",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful operational context that annotations can't express: the public API is closed and keyless calls return 401, requiring your own token. It does not discuss pagination, result caps, or matching behavior (partial vs exact), which are relevant for an open-world search.

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?

Three tight sentences: purpose, return fields, hard prerequisite, then an example. The critical auth constraint is front-loaded in caps and everything earns its place.

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?

Output schema exists so return values needn't be explained, and the description plus annotations plus full schema coverage cover the essentials, including the auth blocker that would otherwise cause 401s. Minor gap: no note on result limits or whether the query is exact-match vs fuzzy, which matters for an open-world name search.

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% and the schema already documents both query and _apiKey including a signup URL. The description's only added param value is restating the token requirement and giving the _apiKey literal in the example, which is marginal beyond the schema.

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: 'Search company officers and directors by name.' It enumerates the returned fields (name, position, company, dates, nationality), which differentiates it from company-oriented siblings, though it never names a sibling like open_corporates_search_companies to contrast the officer-vs-company scope.

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?

Provides a concrete example invocation and implies the use case (looking up an officer by name), but gives no explicit when-to-use/when-not guidance versus the company search siblings. The agent must infer that officer-name searches belong here and company-name searches elsewhere.

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.