Skip to main content
Glama

BRAINIAC Company Intelligence

Search companies

company-intelligence_search

Search companies by name and country using the GLEIF LEI database. Price $0.01 USDC. POST /api/v1/company-intelligence/search. Unpaid calls return 402 and do not run.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden; it discloses cost ($0.01 USDC), the transport (POST /api/v1/company-intelligence/search), and the exact failure mode (unpaid calls return HTTP 402 and do not execute). What it omits is return shape, result ordering, and whether matching is exact or fuzzy — meaningful gaps for a paid search endpoint, but the payment behavior is unusually well disclosed.

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?

Three short sentences, front-loaded with the purpose followed by price and then the failure mode; nothing is padded. The raw endpoint path is the least essential element but still serves a routing/payment purpose.

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

Completeness3/5

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

For a three-parameter paid search tool with no annotations and no output schema, the definition covers purpose and payment but leaves the agent guessing about returned fields, result ordering, and whether the name query supports partial matching. Adequate to invoke, not adequate to predict the response.

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 0%, so the description must compensate. 'By name and country' does map to the query and country parameters, but it never states that country is an ISO two-letter code (the only hint is minLength/maxLength 2 in the schema) and never mentions the third parameter, limit, or its 1–50 range and default of 20.

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 companies by name and country' — plus the underlying data source (GLEIF LEI database), which distinguishes it from siblings like filings, financials, ownership, and profile. It stops short of naming those siblings explicitly, so the agent must infer that this is the general-purpose entry point.

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

Usage Guidelines2/5

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

There is no statement of when to use this search versus company-intelligence_profile or vat-id-lookup, and no guidance on when the optional country filter should be applied or how the name query is matched. Usage is only implied by the word 'Search'.

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