Skip to main content
Glama

List recent funding rounds

list_recent_raises
Read-onlyIdempotent

Climate and sustainability companies that closed a funding round in the last N days (up to 90), newest first. Each raise has company, amount, currency, amount_usd, round, round_date, detected_date, sectors, countries, investors, source_url (the primary source; null when only a feed is known) and raiselens_url. Also returns totals by sector, country and round. By default only checked company rounds: no funder pages or fund news, no off-sector rows, a source article that names the company, and a round date within 60 days. Each raise also carries hiring (open roles, roles in business development and partnerships, and the careers page) when the company has open roles on file. Optional filters: Raise Lens sector slug, country (ISO-2 or aggregate such as EU, AFRICA, GLOBAL), hiring_only.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days.
limitNoNumber of raises to return.
sectorNoOne Raise Lens sector slug, such as renewable-energy.
countryNoISO-2 code or aggregate (EU, AFRICA, ASIA, LATAM, GLOBAL).
date_basisNoannounced: round date when the source gives one; detected: when Raise Lens picked it up.announced
deals_onlyNofalse also returns funder-page context the classifier filed as investment (programmes, portfolio pages).
hiring_onlyNotrue returns only companies that raised and are now hiring (open roles on file).
checked_onlyNofalse also returns deals that fail the checks (no article URL naming the company, off-sector, fund news, round older than 60 days).

Output Schema

NameRequiredDescriptionDefault
queryYes
raisesYes
scannedYes
summaryYes
excluded_uncheckedYes
excluded_older_roundsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / hiring_only
      Added value: +{
      +  "default": false,
      +  "description": "true returns only companies that raised and are now hiring (open roles on file).",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / query / properties / hiring_only
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / raises / items / properties / hiring
      Added value: +{
      +  "anyOf": [
      +    {
      +      "properties": {
      +        "bd_roles": {
      +          "description": "Open roles in business development, partnerships or fundraising.",
      +          "type": "integer"
      +        },
      +        "careers_url": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "The employer's own careers page or job board."
      +        },
      +        "open_roles": {
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "open_roles",
      +        "bd_roles",
      +        "careers_url"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Raised and now hiring: open roles read from the company's own job board; null when none are on file."
      +}
    • changedOutput schema / properties / raises / items / required
      Previous value: -[
      -  "company",
      -  "amount",
      -  "currency",
      -  "amount_usd",
      -  "round",
      -  "round_date",
      -  "detected_date",
      -  "sectors",
      -  "countries",
      -  "investors",
      -  "source_url",
      -  "raiselens_url",
      -  "title",
      -  "summary",
      -  "kind"
      -]New value: +[
      +  "company",
      +  "amount",
      +  "currency",
      +  "amount_usd",
      +  "round",
      +  "round_date",
      +  "detected_date",
      +  "sectors",
      +  "countries",
      +  "investors",
      +  "source_url",
      +  "raiselens_url",
      +  "title",
      +  "summary",
      +  "kind",
      +  "hiring"
      +]
    • addedOutput schema / properties / summary / properties / now_hiring
      Added value: +{
      +  "description": "Raises whose company has open roles on file.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / sector / description
      Previous value: -"One sector slug (list_sectors)."New value: +"One Raise Lens sector slug, such as renewable-energy."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare a safe read-only, idempotent operation, and the description goes well beyond them: it discloses default filtering behavior, the 60-day check window versus the up-to-90-day look-back, the null semantics of source_url when only a feed is known, the presence of sector/country/round totals, and hiring data attached per raise. These are exactly the behavioral traits an agent cannot get from the annotations.

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 core statement, then defaults, then returned fields, then filters — a sensible order with no filler sentences. The long enumeration of return fields partly duplicates the output schema, so it is slightly longer than strictly necessary.

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

Completeness5/5

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

For an 8-parameter, filter-heavy list tool with an output schema and full annotations, the description covers the defaults, the checked-round criteria, edge cases (null source_url), and the aggregate totals. An agent has everything needed to call it correctly without guessing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description adds real meaning on top by explaining that the default mode corresponds to checked company rounds and by describing country aggregates (EU, AFRICA, GLOBAL) and sector slugs in context. It does not add anything for days, limit, or date_basis beyond what the schema already says.

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?

Opens with a specific verb+resource+scope: climate and sustainability companies that closed a funding round in the last N days (max 90), newest first. It even enumerates the returned fields, so an agent knows exactly what it gets. It does not explicitly name how it differs from sibling search/list tools (e.g. search_opportunities), so it stops short of a 5.

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?

Spells out the default inclusion rules (checked company rounds only: no funder pages, no fund news, no off-sector rows, source article must name the company, round within 60 days) and lists the optional filters. That gives a clear picture of when this tool is the right call, but no alternative tool is named for the cases the defaults exclude.

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