Work Insiders

Recently funded startups and who is hiring

workinsiders_funded_startups

Read-onlyIdempotent

Startups that announced a funding round or filed an SEC Form D in the last 90 days, from the Work Insiders "Just raised" list: amount, round, date, industry, country, investors, executives named in filings, open roles counted daily on the company's own job board, the change since the raise, sample job titles, hiring signals and a 0-100 recruiter fit score. Filterable by industry, stage, country, recency and hiring.

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

Input Schema

Name	Required	Description
`days`	No	Rounds announced in the last N days.
`sort`	No	Sort order. Default newest.
`limit`	No
`query`	No	Free text matched against company name, description, job titles and investors. Optional.
`stage`	No	Round stage.
`offset`	No
`country`	No	Headquarters country, for example "United States", or "europe".
`industry`	No	Industry slug.
`hiring_only`	No	Only companies with open roles on a public job board now.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add data provenance — which it does: SEC Form D filings plus the company's own job board, role counts refreshed daily, and a 0-100 fit score scale. It stops short of stating result caps, freshness caveats, or coverage limits for the 'change since the raise' metric.

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?

Front-loaded with the definition before the long field inventory, and no filler sentences. The return-field list is dense and runs long as a single sentence, but since there is no output schema each clause carries information the agent cannot get elsewhere.

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, describing the returned fields is the right call and it is done thoroughly for a 9-parameter, all-optional query tool. Minor gaps remain: no note on the 90-day/25-limit caps being hard boundaries, no pagination guidance for offset, and no indication of result ordering side effects when hiring_only is combined with sort.

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 coverage is 78%, so the schema already documents days, sort, query, stage, country, industry and hiring_only. The description only gestures at the filter axes ('industry, stage, country, recency and hiring') and adds nothing on sort options, query matching behavior, or pagination via limit/offset — that sentence largely restates the enum fields rather than deepening them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: startups that announced a round or filed SEC Form D in the last 90 days, drawn from a named 'Just raised' list, and enumerates the data returned (amount, round, investors, open roles, fit score). An agent can tell instantly what this retrieves; the sibling tools are tool-directory utilities, so no differentiation is needed.

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?

Usage is only implied via 'Filterable by industry, stage, country, recency and hiring' and the phrase 'recruiter fit score', which hints at recruiting/prospecting use. There is no explicit when-to-use statement, no exclusion criteria, and no mention of how it relates to the sibling search/lookup tools.

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

All Work Insiders 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?