Skip to main content
Glama

Companies Daily – SEC filings of US companies

Company page from SEC filings

get_company
Read-onlyIdempotent

A company by CIK or ticker, as on its Companies Daily page: tickers, exchanges, kind of filer, status, state of incorporation, city and state, SIC code, fiscal year end, last annual and quarterly report, Form D offering figures, XBRL totals, “What this means” notes (facts from filings, no judgement of the stock) and the classified filing history with links to the documents on EDGAR. No names of people.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK, leading zeros optional, e.g. "320193".
tickerNoTicker symbol, e.g. "AAPL" (used when cik is empty).

Output Schema

NameRequiredDescriptionDefault
urlYes
as_ofNo
attributionYes

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?

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new scope constraints: the result is facts from filings with no judgement of the stock, and it deliberately excludes names of people. It does not say what happens when the CIK/ticker is unknown or not found, which is the main remaining behavioral gap.

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 lookup key is front-loaded in the opening clause, but the rest is one dense comma-separated enumeration of a dozen-plus return fields. Since an output schema already exists, much of that enumeration is redundant payload rather than actionable instruction, though it does help an agent judge relevance at a glance.

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 read-only two-parameter lookup with full schema descriptions, annotations, and an output schema, the definition covers scope and content exclusions well. The only material omission is not-found/error behavior, which is minor given the low-risk read-only profile.

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% and both parameters carry pattern, example, and the precedence rule ('used when cik is empty'). The description only restates 'by CIK or ticker' without adding format or precedence detail, so the baseline 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 names the resource (a company) and the two lookup keys (CIK or ticker) and enumerates the returned profile fields, so an agent knows exactly what comes back. It falls short of a 5 because it never distinguishes itself from siblings like get_financials, even though it advertises overlapping content such as XBRL totals, annual/quarterly report references, and Form D figures.

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 statement of alternatives, and no exclusions. An agent has to infer that this is the profile lookup and that get_financials or search_companies serve different needs; nothing in the text routes it.

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