Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Company Profile

get_company_profile
Read-only

Fetch an enriched company profile by ticker symbol to retrieve CIK, exchange, sector, industry, market cap, employee count, fundamentals, and trading-halt status in one lightweight response.

Instructions

Get an enriched company profile by ticker symbol. Returns CIK, exchange, sector, industry, market cap, employee count, description, and other fundamental data in a lightweight response. Includes halted/haltCode/haltedAt trading-halt status on every call (false/null when trading normally); a halted-but-listed ticker reports delisted:false. sharesOutstanding is dated: sharesOutstandingAsOf + sharesOutstandingAsOfKind ("stated" = the issuer's statement date; "checked" = when it was last confirmed against a vendor; "none" = date not recorded) and a vendor-free sharesOutstandingSource. The count is only meaningful with its date. A null count means not measured; it does not mean zero. cik: null is a foreign issuer listed on US OTC that files nothing with the SEC (e.g. PGPHF): name, exchange and country come from reference data and every field Signal8 lacks is null.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., AAPL, TSLA)

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses substantial semantics: halt fields present on every call, the meaning of a halted-but-listed ticker reporting delisted:false, the dating contract for sharesOutstanding (stated/checked/none), and the distinction between null (not measured) and zero. These are exactly the behavioral caveats an agent cannot get from structured fields.

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?

Purpose is front-loaded in the first sentence and the remaining sentences are dense but each carries a distinct semantic rule. The run-on formatting around the sharesOutstanding and cik clauses makes it harder to scan than it needs to be, but little is pure filler.

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 single-parameter, read-only lookup with an output schema, the description covers everything an agent needs: what is returned, when halt data appears, and how to interpret null/dated fields. Nothing material is missing.

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?

With a single parameter at 100% schema description coverage, the schema already documents the ticker format with examples. The description only restates 'by ticker symbol' and adds no syntax or resolution nuances, 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?

Opens with a specific verb+resource ('Get an enriched company profile by ticker symbol') and enumerates the returned fundamentals, so an agent knows exactly what the tool produces. It does not explicitly name a sibling like search_companies as the alternative, but the 'by ticker symbol' scoping implicitly separates it from the search tool.

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: it's clear you call this when you already have a ticker and need profile fundamentals, but there is no explicit when-not guidance and no sibling tool (e.g. search_companies for ticker discovery) is named as an alternative.

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