Skip to main content
Glama

Open Corporates

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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:"..."})

Input Schema

TableJSON 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

TableJSON 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
    • addedInput schema / properties / _apiKey
      Added value: +{
+  "description": "Your OpenCorporates API token (required — get one at https://opencorporates.com/api_accounts/new)",
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnly, openWorld, idempotent, non-destructive. The description adds critical behavioral info: authentication requirement (API key) and return fields. No contradiction; complements annotations well.

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?

The description is two sentences plus an example, front-loaded with purpose, no redundant words. Every sentence adds value.

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?

Given annotations, output schema existence, and schema coverage, the description is complete: it covers purpose, required input, return fields, and authentication. Output schema handles return format details.

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 100% with descriptions for both parameters. The description adds a concrete usage example showing how to pass _apiKey, which is helpful but not essential beyond the schema.

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?

The description states 'Search company officers and directors by name' with clear verb and resource, and lists return fields. It distinguishes from siblings like 'search_companies' and 'search_within' by focusing on officers.

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

Usage Guidelines4/5

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

The description explicitly warns about the required API key and gives a usage example. It does not explicitly mention when to use over alternatives, but the distinct purpose and sibling differentiation are implied.

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

All Open Corporates toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources