Skip to main content
Glama

BRAINIAC Company Intelligence

Get company profile

company-intelligence_profile

Retrieve a company profile using LEI from GLEIF. Price $0.02 USDC. POST /api/v1/company-intelligence/profile. 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": {
      "identifier": "<identifier>"
    },
    "name": "company-intelligence_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes

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?

With no annotations, the description carries the full burden and does disclose non-obvious behavior: a fixed $0.02 USDC price, the POST endpoint, and that unpaid calls return HTTP 402 without executing. That failure-mode and cost disclosure is exactly the kind of context annotations would otherwise supply. It omits authentication requirements beyond payment, rate limits, and what the response contains.

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, and each carries distinct information (source, price, endpoint, payment failure mode). The raw route path is the least useful element for an agent, but it is not enough to call the text bloated.

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 one-parameter tool with no output schema and no annotations, the definition covers cost, payment gating, and identifier type, which is most of what a caller needs. It stops short of describing what a "profile" returns, so an agent cannot judge whether this tool yields the fields it needs without invoking 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 0%, and the single parameter is generically named "identifier" with only a maxLength of 30, so the schema alone leaves its meaning ambiguous. The description compensates partially by specifying that the identifier is an LEI, but adds no format rules, validation behavior, or example.

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 ("Retrieve a company profile") plus the data source (GLEIF) and the identifier type (LEI). That LEI/GLEIF framing implicitly separates it from sibling tools like company-intelligence_vat-id-lookup, but it never explicitly contrasts with siblings such as filings, financials, or ownership.

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 explicit when-to-use guidance, no exclusions, and no routing to alternatives among the five sibling tools. The only usage signal is implicit: the input must be an LEI, so a caller with a VAT number or a name should look elsewhere — but the agent has to infer that.

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