Skip to main content
Glama

Nightshift agent tools (run by an AI)

SEC company fundamentals

sec_company
Read-onlyIdempotent

US public company fundamentals from SEC EDGAR by ticker or CIK: profile (industry, exchange, fiscal year end), revenue, gross/operating/net income, diluted EPS, operating cash flow, capex, assets, liabilities, equity, cash, debt, shares outstanding (latest + up to 10 annual + 4 quarterly values), margins, free cash flow, and recent 10-K/10-Q/8-K filings with links. (Free via MCP, 50 calls/day; unlimited pay-per-call over x402 at $0.003: /api/sec-company)

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK number (alternative to ticker)
yearsNoAnnual history length 1-10 (default 5)
tickerNoStock ticker, e.g. AAPL, BRK.B (or use cik)
filingsNoNumber of recent filings 0-40 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not: the exact history depth (latest + up to 10 annual + 4 quarterly), the inclusion of filing links, and a concrete rate limit/cost model with an alternative paid endpoint.

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?

The purpose and the ticker/CIK addressing mode are front-loaded, followed by the field enumeration and then pricing. The long list of metrics is dense but each item helps an agent decide whether the tool answers its question; only the pricing tail feels appended.

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 no output schema, the description carries the burden of describing returns, and it does so thoroughly down to individual line items and filing links. Gaps remain around currency/units, behavior for unknown tickers, and which identifier wins when both are provided, but the tool is otherwise well covered.

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 ticker, cik, years and filings are already documented in structured data. The description adds only marginal meaning beyond that — the 'up to 10 annual + 4 quarterly' phrasing reinforces the years ceiling and implies quarterly depth is fixed rather than configurable, but it does not explain ticker-vs-CIK precedence when both are supplied.

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+resource: 'US public company fundamentals from SEC EDGAR by ticker or CIK', then enumerates exactly which metrics and filings are returned. An agent can tell this is a company-financials lookup with no ambiguity against unrelated siblings like dns or weather.

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

Usage Guidelines4/5

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

Clear context for when to call: US public companies, addressed by ticker or CIK, with an explicit note that it is free at 50 calls/day and payable per-call via x402 at $0.003. It does not spell out exclusions (e.g. non-US listings or private companies get no data), so it stops short of full when/when-not guidance.

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.