Skip to main content
Glama

list_offerings

Offerings — chains of filings under one SEC registration number — latest activity first. Labels: IPO (first registration with no earlier annual/quarterly report, reached a final prospectus), First-time registration (same, no final prospectus), SPAC, Registered company, Shelf. Statuses: Filed, Amended, Effective, Final prospectus, Withdrawn, Dormant (nothing for 270 days).

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

Input Schema

NameRequiredDescriptionDefault
toNoLast event on or before
fromNoLast event on or after, YYYY-MM-DD
labelNo
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully states the ordering and defines offering labels and statuses, but it does not mention read-only safety, authentication needs, pagination behavior, or return shape.

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 description is dense but front-loaded: it first defines offerings and ordering, then supplies the relevant taxonomy. It is appropriately sized, though the enum value explanations partially repeat what the schema already lists.

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 list tool with no output schema and no annotations, the description is adequate for selecting filters but incomplete. It does not explain return values, pagination, or how this differs from search_filings.

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 only 40%, so the description should compensate. It does add meaning for the label and status enum values, but it leaves the from, to, and limit parameters to the schema's brief descriptions.

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 clearly establishes the resource as SEC offering chains and states the ordering as latest activity first. It does not explicitly distinguish this tool from sibling tools like search_filings, but the purpose of listing offerings is clear.

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 description gives no explicit guidance on when to use list_offerings versus alternatives such as search_filings or get_company. Usage is only weakly implied by the presence of label and status filters.

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