Skip to main content
Glama

Primary Sources

by io.github.simonmak-ascent
OverviewDiscussionsAdmin

sec_edgar_company

Read-onlyIdempotent

US SEC registrant profile plus recent filings by ticker or CIK (free, no key). Resolves a ticker via EDGAR company_tickers.json, then returns name, CIK, SIC, a filings URL and the 25 most recent filings. Use when you know the ticker or CIK; use sec_edgar_fulltext for phrase search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerOrCikYesTicker or CIK, e.g. AAPL or 320193

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesSource payload; fields vary per tool
sourceYesHuman-readable upstream source name
retrievedAtYesISO-8601 timestamp of retrieval

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tickerOrCik / description
      Previous value: -"e.g. AAPL or 320193"New value: +"Ticker or CIK, e.g. AAPL or 320193"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Source payload; fields vary per tool",
+      "type": "object"
+    },
+    "retrievedAt": {
+      "description": "ISO-8601 timestamp of retrieval",
+      "type": "string"
+    },
+    "source": {
+      "description": "Human-readable upstream source name",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "retrievedAt",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description still adds real behavior: it is free and keyless, it resolves tickers through EDGAR company_tickers.json, and it caps results at the 25 most recent filings. It does not cover error behavior for an unknown ticker, which keeps it off a 5.

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?

Three tight sentences: identity/returns first, then the resolution mechanism, then the routing rule. Every clause earns its place and nothing is buried.

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

Completeness5/5

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

A one-parameter lookup with rich annotations and an output schema; the description needn't detail return shapes, and it already names the returned fields and the sibling route. Nothing required for correct invocation is missing.

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 100% and the single parameter is fully documented ('Ticker or CIK, e.g. AAPL or 320193'), so the schema carries the semantics. The description only restates the same alternative, adding no format or edge-case detail. Baseline 3 for near-zero marginal value.

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 SEC registrant profile plus recent filings') with the exact input key (ticker or CIK), and explicitly names the sibling it is not: sec_edgar_fulltext. An agent can distinguish it from the other company-lookup siblings without opening any schema.

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?

Gives an explicit selection rule ('Use when you know the ticker or CIK') plus the alternative for the opposite case ('use sec_edgar_fulltext for phrase search'). When-to-use and when-to-use-something-else are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Primary Sources toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources