Skip to main content
Glama
Dxfory

edgar-filings

by Dxfory
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_trading_symbols

Retrieves common stock ticker symbols from SEC 10-K or 10-Q filings, distinguishing common stock from preferred, notes, or dual-class symbols. Provide a ticker or CIK to get the trading symbol.

Instructions

Every dei:TradingSymbol fact on a 10-K or 10-Q, plus the legacy entity_info ticker scalar.

Use this when you need the common stock ticker versus preferred, notes, or dual-class symbols. ticker_or_cik: ticker like NVDA or a CIK. accession: optional filing accession; default is the latest of form. form: 10-K (default) or 10-Q.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formNo10-K
accessionNo
ticker_or_cikYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / form
      Added value: +{
+  "default": "10-K",
+  "title": "Form",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does disclose the data scope, default accession behavior, and accepted identifier types (ticker or CIK). However, it omits output structure, error behavior, and whether the result is a list or a scalar structure, which are notable gaps for an unannotated tool.

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

Conciseness5/5

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

The description is four short lines with no redundant sentences. It front-loads the purpose, then the usage condition, then parameter semantics. Each sentence earns its place and the structure is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description covers the input side well but leaves the return shape under-specified. The agent knows it will get 'every fact' and a scalar, but not whether the return is an array, object, or how symbols are keyed. Given the tool's relative simplicity, this is a moderate gap, so a middle score is appropriate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by explaining every parameter: ticker_or_cik with an example ('NVDA' or a CIK), accession as optional with a default of the latest filing of form, and form with allowed values ('10-K' default or '10-Q'). This gives an agent everything needed to fill arguments correctly.

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?

The first sentence explicitly states the tool retrieves every dei:TradingSymbol fact from 10-K/10-Q filings plus the legacy entity_info ticker scalar. This is a clear verb+resource with a precise scope, and the use-case line ('common stock ticker versus preferred, notes, or dual-class symbols') distinguishes it from sibling tools covering revenue, nonaccrual, and form4 data. No ambiguity remains.

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?

The description gives an explicit trigger: 'Use this when you need the common stock ticker versus preferred, notes, or dual-class symbols.' This states both the when and the when-not (anything other than common stock ticker). It also clarifies parameter defaults and accepted formats, giving the agent enough to decide to call it without opening schemas.

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