Palanor

palanor_get_form_d_offerings

U.S. private offerings from SEC Form D filings (2009 onward), refined by Palanor. One row per offering, as of its latest filing: issuer, CIK, state, industry group, exemptions, amounts offered and sold, investors, whether it is venture-like, the SEC filing link, and Palanor's AI classification of the issuer (class, method, confidence, evidence URL). Newest filing first. Requires a Pro or Enterprise key.

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": "palanor_get_form_d_offerings"
  }
}

Input Schema

Name	Required	Description
`ai`	No	true: only issuers Palanor classes as AI; false: only issuers classed not AI.
`to`	No	Latest filing on or before, YYYY-MM-DD.
`cik`	No	Issuer CIK.
`from`	No	Latest filing on or after, YYYY-MM-DD.
`limit`	No	Rows, 1–100 (default 25).
`state`	No	Issuer state or country code as filed, e.g. CA.
`offset`	No	Rows to skip (default 0).
`min_amount`	No	Minimum total amount sold, USD.
`venture_only`	No	Only venture-like offerings (private U.S. operating companies selling equity under Rule 506).
`industry_group`	No	Form D industry group, e.g. "Other Technology", "Biotechnology".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses coverage start date, that rows are deduplicated to the latest filing per offering, the sort order (newest filing first), and an access-tier requirement. It does not mention pagination ceiling behavior beyond the schema or rate limits, which keeps it short of a 5.

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?

A single dense sentence plus a sort-order clause and an access note; no filler, and the resource identity is front-loaded before the field enumeration.

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?

No output schema exists, so the description usefully enumerates the returned fields (issuer, CIK, exemptions, amounts, AI classification with confidence and evidence URL). For a 10-parameter read tool with zero annotations this is nearly sufficient; only auth mechanics and pagination behavior remain underspecified.

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 every filter is already documented with format hints (YYYY-MM-DD, CA, limit 1-100). The description adds no per-parameter meaning beyond the schema and only frames the overall filterable surface, which is the correct baseline when the schema does the heavy lifting.

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 resource and scope: 'U.S. private offerings from SEC Form D filings (2009 onward)' with one row per offering as of its latest filing. The row-grain statement implicitly distinguishes it from the issuer-level sibling palanor_get_form_d_issuer, but it never names that alternative, so an agent must infer the split.

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?

The description gives a useful prerequisite ('Requires a Pro or Enterprise key') and implies a filtered search over offerings, but it never states when to choose this tool over palanor_get_form_d_issuer, palanor_get_private_funds, or palanor_find_entities. Usage is inferable from the description but not directed.

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

All Palanor tools Inspect

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

Need Help?