Skip to main content
Glama

AIsa Equities

by one.aisa
OverviewDiscussionsAdmin

Get Company SEC Filings

get_financial_filings
Read-onlyIdempotent

Get SEC filings for a company.

Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
cikNoThe Central Index Key (CIK) of the company.
limitNoThe maximum number of filings to return (default: 10). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`. Provider reference (supplier schema): `{"default":10,"minimum":1,"type":"integer"}`.
cursorNoOpaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.
tickerNoThe ticker symbol.
filing_typeNoFilter by one or more filing types. Repeat the query parameter to pass multiple values (e.g. filing_type=10-Q&filing_type=10-K).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cik
      Added value: +{
+  "description": "The Central Index Key (CIK) of the company.",
+  "type": "string"
+}
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
+  "type": "string"
+}
    • addedInput schema / properties / filing_type
      Added value: +{
+  "description": "Filter by one or more filing types. Repeat the query parameter to pass multiple values (e.g. filing_type=10-Q&filing_type=10-K).",
+  "items": {
+    "enum": [
+      "10-K",
+      "10-Q",
+      "20-F",
+      "6-K",
+      "8-K"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / limit / description
      Added value: +"The maximum number of filings to return (default: 10). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.\n\nProvider reference (supplier schema): `{\"default\":10,\"minimum\":1,\"type\":\"integer\"}`."
    • addedInput schema / properties / ticker / description
      Added value: +"The ticker symbol."
  2. Changed7 schema fields changed
    • removedInput schema / properties / cik
      Removed value: -{
-  "description": "The Central Index Key (CIK) of the company.",
-  "type": "string"
-}
    • removedInput schema / properties / filing_type
      Removed value: -{
-  "description": "Filter by one or more filing types. Repeat the query parameter to pass multiple values (e.g. filing_type=10-Q&filing_type=10-K).",
-  "items": {
-    "enum": [
-      "10-K",
-      "10-Q",
-      "8-K",
-      "20-F",
-      "6-K"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / limit / default
      Removed value: -10
    • removedInput schema / properties / limit / description
      Removed value: -"The maximum number of filings to return (default: 10)."
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"string"
    • removedInput schema / properties / ticker / description
      Removed value: -"The ticker symbol."
  3. Changed7 schema fields changed
    • addedInput schema / properties / cik
      Added value: +{
+  "description": "The Central Index Key (CIK) of the company.",
+  "type": "string"
+}
    • addedInput schema / properties / filing_type
      Added value: +{
+  "description": "Filter by one or more filing types. Repeat the query parameter to pass multiple values (e.g. filing_type=10-Q&filing_type=10-K).",
+  "items": {
+    "enum": [
+      "10-K",
+      "10-Q",
+      "8-K",
+      "20-F",
+      "6-K"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / limit / default
      Added value: +10
    • addedInput schema / properties / limit / description
      Added value: +"The maximum number of filings to return (default: 10)."
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"string"New value: +"integer"
    • addedInput schema / properties / ticker / description
      Added value: +"The ticker symbol."
  4. Changed7 schema fields changed
    • removedInput schema / properties / cik
      Removed value: -{
-  "description": "The Central Index Key (CIK) of the company.",
-  "type": "string"
-}
    • removedInput schema / properties / filing_type
      Removed value: -{
-  "description": "Filter by one or more filing types. Repeat the query parameter to pass multiple values (e.g. filing_type=10-Q&filing_type=10-K).",
-  "items": {
-    "enum": [
-      "10-K",
-      "10-Q",
-      "8-K",
-      "20-F",
-      "6-K"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / limit / default
      Removed value: -10
    • removedInput schema / properties / limit / description
      Removed value: -"The maximum number of filings to return (default: 10)."
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"string"
    • removedInput schema / properties / ticker / description
      Removed value: -"The ticker symbol."
  5. First observed

TDQS

B3.2/5.0
Behavior3/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 only added behavioral content is the pricing note ($0.02 per successful request), which is genuinely useful cost context but is boilerplate rather than tool-specific behavior; nothing is said about coverage limits or what happens when all optional filters are omitted.

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?

A single front-loaded sentence with no filler, and the pricing note is confined to a delimited block. It is terse to the point of under-specification, but nothing present is wasted.

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 and the parameters are fully documented, so the description needn't explain returns. However, with zero required parameters and many overlapping siblings, the description should at least say how to scope a request or when this differs from get_financial_filings_items.

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%, including pagination semantics for limit and the opaque cursor, so the schema does the heavy lifting. The description adds nothing beyond that, which is the baseline expectation.

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?

States a specific verb and resource ('Get SEC filings for a company'), so the agent knows exactly what the tool returns. It does not distinguish itself from close siblings such as get_financial_filings_items or edinet_filings_digest, which is the only gap at this level.

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, no prerequisites, and no mention of alternatives despite a large sibling set covering overlapping financial data. The agent must infer usage entirely from the name and schema.

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

All AIsa Equities 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