Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_sec_8k_nih_triggers

Read-onlyIdempotent

Track real-time SEC 8-K buying triggers and commercial NIH SBIR/STTR biotech grants to surface C-suite changes, M&A closings, material contracts, and grant awards for lead generation.

Instructions

Track real-time SEC Form 8-K enterprise buying triggers (Item 5.02 C-suite changes, Item 2.01 M&A closings, Item 1.01 material contracts) and commercial NIH SBIR/STTR biotech grant awards (corridordata/sec-8k-nih-enterprise-triggers).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_sec_8k_nih_triggers"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourcesNoTrigger feeds to query.
daysBackNoSEC 8-K lookback window in days.
maxItemsNoMaximum corporate or biotech trigger signals to return.
sec8kItemCodesNoSEC 8-K item codes (e.g. ['5.02', '2.01', '1.01']).
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).
commercialBiotechSbirOnlyNoRestrict NIH grants to commercial private-sector SBIR/STTR biotech companies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 description adds 'real-time' freshness and the actor identifier, but says nothing about result volume, pagination, or that billing is pay-per-event (that detail lives only in the schema).

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 the primary resource and item codes first, then the secondary grant feed. The parenthetical actor slug is useful provenance but slightly clutters the read; nothing is padded.

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?

With six optional parameters, no output schema, and only a one-line description, an agent lacks any picture of what a returned 'trigger signal' contains or how the two feeds are merged into results. Adequate to select the tool, thin for interpreting its output.

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 six parameters. The description corroborates the item-code values and the commercial biotech restriction, but adds no format or syntax detail beyond what the schema provides, so the baseline applies.

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 ('Track') plus two concrete resources: SEC Form 8-K items (5.02, 2.01, 1.01) and NIH SBIR/STTR biotech grants, with the backing actor slug. An agent knows exactly what data domain this covers, though it does not explicitly contrast itself with sibling award/tender tools like search_us_federal_awards.

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?

The phrase 'enterprise buying triggers' hints at a sales-intelligence use case, but there is no explicit when-to-use condition, no prerequisites, and no named alternative or exclusion. The agent must infer selection from the grants/tenders sibling list on its own.

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