Skip to main content
Glama

Companies Daily – SEC filings of US companies

Daily editions

list_editions
Read-onlyIdempotent

EDGAR business days with an edition, newest first: state (ready or open), companies with classified filings, bankruptcies, late filings, delisting notices, leadership changes, IPOs, private raises.

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_editions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
urlYes
as_ofNo
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety and mutability need no restating. The description does add real behavioral context beyond them: results are ordered 'newest first' and each edition carries a state of 'ready' or 'open'. It stops short of describing pagination behavior or what happens when fewer editions exist than requested.

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?

It is a single compact sentence with no filler, and the ordering fact is placed usefully. But the long enumeration of content categories absorbs nearly the whole budget while usage and parameter guidance go unmentioned, and the fragment lacks a leading verb to orient the reader.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile — which lowers the bar. For a one-parameter list tool, though, the absence of any usage discrimination from the sibling read tool and any mention of the limit parameter leaves meaningful gaps.

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

Parameters2/5

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

There is a single parameter (limit, default 14, max 60, min 1) with 0% schema description coverage, so the description bears the burden of explaining it — and it says nothing about limiting result count. With low coverage and no compensating explanation, the agent gets bounds from the schema but no meaning or guidance on choosing a value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ('EDGAR business days with an edition, newest first') and enumerates what an edition contains, so an agent can infer it returns a list of editions. However, it is a noun-phrase fragment with no verb, and it never explicitly states that this is the list endpoint versus the single-edition sibling 'get_daily_edition'. The purpose is inferable but not stated.

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 when-to-use guidance at all: no statement of prerequisites, no distinction from get_daily_edition, list_events, or list_event_types, and no advice on how to choose between them. The agent must infer usage purely from the tool name and the enumerated contents.

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