Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Look up a company or person

resolve
Read-onlyIdempotent

Look up a company, person, investor or institution and get its canonical id: {node_id, node_type, name} (every match in candidates when ambiguous; a person name returns up to 5 namesakes, each with cik, current_company and current_title to tell them apart). For a LIST of people, use resolve_people (one call, matched against each company's roster). Best for tickers, CIKs, CRDs, web domains, LinkedIn URLs and company names; person names work too ('Colette Kress', 'Kress, Colette', 'KRESS COLETTE M'). Most tools take a ticker or CIK directly, so you don't need this first. To find people by name with filters (company, title, school), use a people-search tool instead. For a biotech gene/target/indication name (e.g. 'PD-1', 'HER2') pass kind='gene' — a different identifier space (HGNC symbols), returns {canonical, hgnc_id, aliases, confidence, kind} candidates.

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": "resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoSet to 'gene' to resolve a biotech gene/target/modality/indication name (HGNC symbols) instead of a company/person/investor/institution.
identifierYesticker / cik / domain / crd / linkedin_url / name — or a gene/target/indication name when kind='gene'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further by disclosing ambiguity behavior (all matches returned in candidates; up to 5 namesakes with cik, current_company and current_title) and a divergent return shape for the gene mode. That is exactly the kind of context annotations cannot carry.

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?

Front-loaded with purpose and return shape, and every clause carries routing information. The single dense paragraph with stacked parentheticals makes it slightly harder to scan than it needs to be, but there is no filler.

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?

For a two-parameter lookup with no output schema, the description supplies both the normal and gene-mode return shapes and the disambiguation behavior, which is enough to call it correctly. The only residual gap is that it doesn't state what happens when nothing matches.

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%, so the baseline is 3; the description adds some value by enumerating accepted identifier formats and by showing name-order variants ('Kress, Colette', 'KRESS COLETTE M') plus the gene identifier space. It does not, however, add syntax or normalization rules beyond those examples.

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?

States a specific verb (look up) plus the exact resource classes (company, person, investor, institution) and the returned shape {node_id, node_type, name}. It explicitly distinguishes itself from resolve_people, people-search tools, and the kind='gene' path, so an agent can pick it without opening a schema.

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

Usage Guidelines5/5

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

Names concrete inputs it is best for (tickers, CIKs, CRDs, web domains, LinkedIn URLs, company names) and gives an explicit when-not: 'Most tools take a ticker or CIK directly, so you don't need this first.' It routes to specific alternatives for the two adjacent cases: a list of people (resolve_people) and filtered people 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