Skip to main content
Glama
Sign In

Gouda Studios Agent Tools

by app.vercel.gouda-studios-agent-tools
OverviewDiscussionsAdmin

gouda_studios/sec-edgar-filings-feed

gouda_studios--sec-edgar-filings-feed
Destructive

Returns SEC EDGAR filings for tickers or CIKs (8-K, 10-Q, 10-K, Form 4, Form D, S-1) with filing dates and document links. Use for company filing monitoring.

Input Schema

NameRequiredDescriptionDefault
ciksNoOptional SEC Central Index Keys, e.g. ["320193"]. Leave.
onlyNewNoIf true, return only notices not seen before.
tickersNoOptional stock tickers, e.g. ["AAPL","NVDA"]. Resolved.
waitSecsNoSeconds to wait for the run to finish (0-45).
formTypesNoForm types to include, .
maxResultsNoMaximum notices to return.
contactEmailNoOptional. SEC asks automated clients to identify.
filedWithinDaysNoOnly filings from the last N days. 0 = no limit (company.

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value.
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT |.
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states.
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed46 schema fields changed
    • changedInput schema / description
      Previous value: -"Returns SEC EDGAR filings as one JSON row per filing, from official sec.gov / data.sec.gov endpoints. With tickers or CIKs it reads each company's filing history; with neither it returns the latest market-wide filings of the chosen form types. Example: {\"tickers\":[\"AAPL\",\"TSLA\"],\"formTypes\":[\"8-K\",\"10-Q\"],\"filedWithinDays\":30}. Pricing: $0.002 per filing row."New value: +"Returns SEC EDGAR filings as one JSON row per filing."
    • removedInput schema / properties / ciks / default
      Removed value: -[]
    • changedInput schema / properties / ciks / description
      Previous value: -"Optional SEC Central Index Keys, e.g. [\"320193\"]. Leave tickers and CIKs empty to get latest filings across all companies."New value: +"Optional SEC Central Index Keys, e.g. [\"320193\"]. Leave."
    • removedInput schema / properties / ciks / items / description
      Removed value: -"Optional SEC Central Index Keys, e.g. [\"320193\"]. Leave tickers and CIKs empty to get latest filings across all companies."
    • removedInput schema / properties / ciks / items / title
      Removed value: -"CIK numbers"
    • removedInput schema / properties / ciks / title
      Removed value: -"CIK numbers"
    • changedInput schema / properties / contactEmail / description
      Previous value: -"Optional. SEC asks automated clients to identify themselves; this email is sent in the User-Agent header to sec.gov only."New value: +"Optional. SEC asks automated clients to identify."
    • removedInput schema / properties / contactEmail / title
      Removed value: -"Contact email for SEC User-Agent"
    • changedInput schema / properties / filedWithinDays / description
      Previous value: -"Only filings from the last N days. 0 = no limit (company mode returns the ~1000 most recent).\nExample values: 7"New value: +"Only filings from the last N days. 0 = no limit (company."
    • removedInput schema / properties / filedWithinDays / examples
      Removed value: -[
-  7
-]
    • removedInput schema / properties / filedWithinDays / title
      Removed value: -"Filed within (days)"
    • removedInput schema / properties / formTypes / default
      Removed value: -[]
    • changedInput schema / properties / formTypes / description
      Previous value: -"Form types to include, e.g. [\"8-K\",\"10-K\",\"10-Q\",\"4\",\"D\",\"S-1\",\"13F-HR\",\"SC 13D\"]. Empty = all forms (company mode only; market-wide mode needs at least one).\nExample values: [\"8-K\"]"New value: +"Form types to include, ."
    • removedInput schema / properties / formTypes / examples
      Removed value: -[
-  "8-K"
-]
    • removedInput schema / properties / formTypes / items / description
      Removed value: -"Form types to include, e.g. [\"8-K\",\"10-K\",\"10-Q\",\"4\",\"D\",\"S-1\",\"13F-HR\",\"SC 13D\"]. Empty = all forms (company mode only; market-wide mode needs at least one)."
    • removedInput schema / properties / formTypes / items / title
      Removed value: -"Form types"
    • removedInput schema / properties / formTypes / prefill
      Removed value: -[
-  "8-K"
-]
    • removedInput schema / properties / formTypes / title
      Removed value: -"Form types"
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum rows (1-5000). You pay per row, so this caps cost: 100 rows = $0.20.\nExample values: 100"New value: +"Maximum notices to return."
    • removedInput schema / properties / maxResults / examples
      Removed value: -[
-  100
-]
    • removedInput schema / properties / maxResults / title
      Removed value: -"Max results"
    • changedInput schema / properties / onlyNew / description
      Previous value: -"true = skip filings delivered by an earlier run with the same tickers/CIKs/forms. Use with a schedule for an alert feed."New value: +"If true, return only notices not seen before."
    • removedInput schema / properties / onlyNew / title
      Removed value: -"Only new since last run"
    • removedInput schema / properties / tickers / default
      Removed value: -[]
    • changedInput schema / properties / tickers / description
      Previous value: -"Optional stock tickers, e.g. [\"AAPL\",\"NVDA\"]. Resolved to CIKs with the SEC ticker file.\nExample values: [\"AAPL\",\"TSLA\"]"New value: +"Optional stock tickers, e.g. [\"AAPL\",\"NVDA\"]. Resolved."
    • removedInput schema / properties / tickers / examples
      Removed value: -[
-  "AAPL",
-  "TSLA"
-]
    • removedInput schema / properties / tickers / items / description
      Removed value: -"Optional stock tickers, e.g. [\"AAPL\",\"NVDA\"]. Resolved to CIKs with the SEC ticker file."
    • removedInput schema / properties / tickers / items / title
      Removed value: -"Tickers"
    • removedInput schema / properties / tickers / prefill
      Removed value: -[
-  "AAPL",
-  "TSLA"
-]
    • removedInput schema / properties / tickers / title
      Removed value: -"Tickers"
    • changedInput schema / properties / waitSecs / description
      Previous value: -"Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget."New value: +"Seconds to wait for the run to finish (0-45)."
    • changedOutput schema / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."
    • changedOutput schema / properties / exitCode / description
      Previous value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."
    • changedOutput schema / properties / status / description
      Previous value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."
    • changedOutput schema / properties / storages / description
      Previous value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."
    • changedOutput schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."
    • changedOutput schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / description
      Previous value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."
    • changedOutput schema / properties / storages / properties / datasets / description
      Previous value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / description
      Previous value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."
    • changedOutput schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."
    • changedOutput schema / properties / storages / properties / keyValueStores / description
      Previous value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."
    • changedOutput schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / description
      Previous value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."
    • changedOutput schema / properties / tip / description
      Previous value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."
    • changedOutput schema / properties / tip / properties / caveat / description
      Previous value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."
    • changedOutput schema / properties / tip / properties / message / description
      Previous value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The annotations declare readOnlyHint=false and destructiveHint=true, which is a surprising profile for a 'returns filings' feed, and the description does nothing to explain or reconcile it (e.g., that invoking it starts a billable actor run that writes to a dataset). It also silently omits the async run model implied by waitSecs and the stateful filtering implied by onlyNew, so the agent cannot tell that repeated calls with onlyNew=true yield different results.

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?

Two tight sentences with the resource and its supported form types front-loaded, followed by a usage cue. No filler, though the form-type list is somewhat redundant with the schema title.

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 covers return shape, so the description needn't explain results, and safety hints are in annotations. But for an 8-parameter, run-based tool with zero required inputs, the description leaves the default invocation and the meaning of an empty parameter set unaddressed.

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 the schema already documents all eight parameters; the description only echoes the tickers/CIKs inputs and form-type list. Baseline 3 applies — no added syntax, resolution rules, or guidance on interplay between filedWithinDays and onlyNew.

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?

Names a specific verb and data source ('Returns SEC EDGAR filings'), and enumerates the concrete form types (8-K, 10-Q, 10-K, Form 4, Form D, S-1) plus the two query keys (tickers/CIKs). This makes it trivially distinguishable from the other sibling feeds (GLEIF, SAM.gov, USAspending), though it never names a sibling.

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?

'Use for company filing monitoring' gives a use-case frame, but there is no when-not guidance, no mention of what to do if you only have a company name, and no statement of which of tickers vs ciks to supply (or what happens if neither is given, since all 8 params are optional).

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

All Gouda Studios Agent Tools 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