Skip to main content
Glama

Primary Sources

by io.github.simonmak-ascent
OverviewDiscussionsAdmin

sec_edgar_fulltext

Read-onlyIdempotent

Full-text search US SEC EDGAR filings (free, no key). Searches the EDGAR full-text index and returns matching filings with form type, filing date, CIK and an Archives URL. Use for primary-source corporate disclosures when you have a phrase or company name but not a ticker. For a known ticker or CIK, prefer sec_edgar_company.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formsNoComma-separated form types, e.g. 6-K,10-K,8-K
queryYesPhrase to search, e.g. "Hong Kong" or a company name
dateRangeNoDate range e.g. 2026-01-01,2026-09-26, or "custom"

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 / dateRange / description
      Previous value: -"e.g. 2026-01-01,2026-09-26 or \"custom\""New value: +"Date range e.g. 2026-01-01,2026-09-26, or \"custom\""
    • 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 and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond that: it is free with no key required, which matters for an agent deciding whether it can call it. It does not mention rate limits, but for a well-annotated read-only search this is a solid disclosure.

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 tightly written sentences, front-loaded with purpose, then capability, then routing. Every sentence earns its place and none repeats structured data.

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?

With an output schema covering return values, full parameter coverage, and rich annotations, the description supplies exactly the extra context needed: cost/auth ('free, no key') and sibling routing. Nothing required to select or call the tool 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%, so all three parameters (query, forms, dateRange) are already documented in the schema. The description adds no syntax or format detail beyond it, so the baseline 3 is appropriate.

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 description states a specific verb and resource ('Full-text search US SEC EDGAR filings') plus the index searched, and explicitly distinguishes itself from the sibling 'sec_edgar_company'. An agent can identify the tool's function and scope without opening the 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?

It gives the exact usage condition ('when you have a phrase or company name but not a ticker') and names the alternative with its own condition ('For a known ticker or CIK, prefer sec_edgar_company'). This is explicit routing with no inference required.

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