Skip to main content
Glama

Company Registry Lookup (US states + LEI)

Company registry lookup (US states + global LEI)

search_companies
Read-only

Search official business registries (NY, CO, OR, CT, PA) and the GLEIF LEI index for a company name. Returns status, entity type, formation date, address, registered agent and officers where published. Takes ~5-10s. $0.02 per call after the free daily quota.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name; include the distinctive first words
limitNoMax results per registry, default 5
sourcesNoRegistries to search (default all): NY, CO, OR, CT, PA, LEI
min_scoreNoName similarity threshold, default 0.8

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only/open-world safety profile, and the description adds genuinely new operational context: a ~5-10s latency expectation, a $0.02 per-call cost after the free daily quota, and the caveat that officer/agent data appears only 'where published.' That cost and partial-data disclosure is exactly the kind of trait 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: scope first, return fields second, operational cost/latency last. Every clause carries information an agent would otherwise have to discover by trial, and nothing is repeated from the schema or annotations.

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?

For a read-only multi-registry search with no output schema, the description supplies the missing return-field information, the partial-coverage caveat, and the cost/latency trade-off. Combined with a fully documented input schema, an agent has everything needed to call it correctly and budget for it.

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 description coverage is 100%, so the schema already documents `name`, `limit`, `sources`, and `min_score`. The description echoes the registry set already enumerated in the `sources` enum but adds no meaning for `limit` or `min_score`, so 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?

The definition gives a specific verb and resource ('Search official business registries ... and the GLEIF LEI index for a company name') and enumerates exactly which registries are covered. It also lists the fields returned, so an agent knows the shape of the output. It never names the sibling list_company_sources, so there is no explicit routing cue, though the required `name` input implicitly separates searching from listing sources.

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?

Usage is implied rather than stated: an agent can infer 'call this when you have a company name and want registry data.' There is no explicit when-not guidance, no mention of when to prefer list_company_sources first, and no advice on narrowing `sources` to save cost or latency.

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