Skip to main content
Glama

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

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, non-destructive behavior, so the description is not obligated to restate safety. It adds real value beyond them by disclosing the upstream source (SEC EDGAR EFTS) and a per-call price of $0.10 USDC, which affects an agent's willingness to call repeatedly. It stops short of describing result volume, pagination, or latency for a full-text search over a 90-day window.

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 short sentences, front-loaded with the usage trigger and immediately followed by what is returned, the source, and the cost. No filler or redundant restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does its job by stating what comes back, from where, and at what price. The main remaining gap is parameter coverage: the mandatory window parameter and the offering-size floor are undocumented anywhere, which matters for correct invocation.

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 must carry parameter meaning and largely does not. It mentions only the optional state and SIC filters, leaving the required 'days_back' (1-90 window) and 'min_offering_usd' entirely unexplained, including the 2-character state constraint and the 90-day ceiling.

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?

The description names a specific verb and resource ('Returns Form D filings from EDGAR full-text search') and frames the trigger domain as new private placement activity. It is unambiguous about the data source and the subject matter, though it does not compare itself to any sibling tool by name.

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?

'Use when tracking new private placement activity ... in a recent window' gives a clear triggering condition with an implicit recency constraint. There is no explicit when-not guidance or named alternative, but the intended context is easy to infer.

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