Skip to main content
Glama

Stratalize Intelligence

Get Form D New Raises

get_form_d_new_raises
Read-only

Use when tracking new private placement activity via SEC Form D filings in a recent window. Returns Form D filings from EDGAR full-text search with optional state and SIC filters. Source: SEC EDGAR EFTS. $0.10 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days_back": "<days_back>"
    },
    "name": "get_form_d_new_raises"
  }
}

Input Schema

NameRequiredDescriptionDefault
sicNo
stateNo
days_backYes
min_offering_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that — the upstream source (SEC EDGAR EFTS) and a per-call price of $0.10 USDC — but it does not say what the 'full-text search' is actually searching on, how many filings come back, or whether results are truncated.

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?

Three short sentences, with the usage trigger and the returned resource front-loaded ahead of sourcing and pricing details. Nothing is wasted, though the last two sentences are fragments that could be merged without loss.

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?

For a read-only, four-parameter tool with no output schema, the description covers what the tool is and roughly when to call it, but leaves the agent guessing on return cardinality, pagination, and the meaning of min_offering_usd. Adequate to invoke, not sufficient to predict output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it only partially delivers: it mentions state and SIC filters and implies a recency window (days_back), but never explains min_offering_usd at all. It also omits practical format constraints such as the 2-character state code and the 90-day ceiling on days_back.

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 concrete resource and method: Form D filings pulled from EDGAR full-text search, scoped to a recent window. The resource is distinct enough from sibling tools (litigation alerts, 13F holdings, 8-K events) that an agent can pick it out, though it never names a sibling or an explicit non-overlap boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger: 'Use when tracking new private placement activity... in a recent window,' which tells the agent the scenario clearly. There are no when-not conditions and no named alternative for the adjacent use cases (e.g., older filings or historical raises), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources