Skip to main content
Glama

Companies Daily – SEC filings of US companies

Companies in a US state

get_state_summary
Read-onlyIdempotent

SEC filings of companies with a business address in one state (or DC): event counts since the start of the data, the latest bankruptcies and delisting notices, late filings, raises and IPOs, leadership changes, and cities with a page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "get_state_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesState of the business address: slug ("california") or USPS code ("CA").

Output Schema

NameRequiredDescriptionDefault
urlYes
as_ofNo
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description contributes the temporal scope ('since the start of the data') and the category breadth of the response, but adds nothing about rate limits, freshness, or what happens for states with no data.

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?

Front-loaded with the defining scope clause before the colon, so the reader gets the core identity in the first seven words. The trailing enumeration is long and partly duplicates what the output schema already exposes.

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?

A single required parameter, full annotations, and an output schema mean the description only needs to establish scope and it does. The one real gap is routing guidance versus sibling search tools.

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 the state parameter already documents both slug and USPS code formats with a max length. The description only adds the '(or DC)' note about accepted scope, which is marginal beyond the schema.

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 a specific resource and scope: SEC filings of companies with a business address in one state, plus the aggregate payload it returns. It is clearly distinguishable from company-level siblings like get_company, though it never names an alternative to contrast against.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the state-level rollup to call instead of per-company lookups, but there is no explicit when-to-use, when-not, or named alternative such as search_companies for company-level queries.

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