Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Institution Detail

get_institution_detail
Read-only

Retrieve an institutional investor's profile by SEC CIK number, including total AUM, holdings count, and filing history for financial research.

Instructions

Get detailed information about a specific institutional investor by their SEC CIK number. Returns the institution name, total AUM, number of holdings, and filing history. Takes the institution's CIK.

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

Input Schema

NameRequiredDescriptionDefault
cikYesSEC CIK number of the institution (e.g., "0001067983" for Berkshire Hathaway)

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds a brief enumeration of what is returned (name, AUM, holdings count, filing history), but reveals nothing about auth needs, rate limits, or behavior when a CIK is unknown or unformatted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first two sentences are well front-loaded and efficient. The closing sentence 'Takes the institution's CIK.' duplicates information already given in sentence one and does not earn its place.

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?

With one fully documented parameter, complete annotations, and an output schema handling return values, the description covers nearly everything needed to invoke the tool correctly. The remaining gap is relational context: how this differs from the many other get_institution_* siblings that take the same identifier.

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% and the single parameter already documents the CIK format plus a Berkshire Hathaway example. The description's 'Takes the institution's CIK' adds no meaning beyond the schema, so the baseline of 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 description states a specific verb and resource ('Get detailed information about a specific institutional investor') and pins the identifier ('by their SEC CIK number'), which distinguishes it from list-style siblings like get_institutions or search_institutions. It stops short of naming a sibling explicitly, so differentiation is inferred rather than stated.

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?

The only usage instruction is 'Takes the institution's CIK,' which is a restatement of the required parameter, not guidance. Nothing tells the agent when to prefer this over get_institutions, search_institutions, get_institution_holdings, or get_institution_filings, which all operate on the same entity.

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

Deploy Server

Other Tools