Skip to main content
Glama

AI Capital Index

get_ai_funding_rounds

AI funding rounds of $25M+ with lead investors, confirmed valuations and sources. Requires a Funding, Team or Institutional 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": "get_ai_funding_rounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoYYYY-MM-DD
categoryNomodels, infra, tooling, application, robotics, other
investorNo
min_amountNoMinimum round size in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real context: a hard $25M+ floor, inclusion criteria (lead investors, confirmed valuations, sources), and an access prerequisite ('Requires a Funding, Team or Institutional key'). However, it never says whether results are paginated, in what order they return, or what happens when min_amount conflicts with the stated $25M+ floor, and the 'key' requirement is vague about whether it is a credential tier or an argument.

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?

Two sentences, both front-loaded with the highest-value facts — data scope first, prerequisite second. No filler or repetition of the tool name.

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 4-parameter list tool with no annotations and no output schema, the description covers data scope and access requirements but omits pagination/result-size behavior and leaves the prerequisite key ambiguous. It is workable but leaves gaps an agent must discover by failing a call.

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 75%, so baseline is 3; the description adds little meaning beyond the schema. The unlabeled 'investor' parameter is not clarified (lead investor only?), and the stated '$25M+' floor creates ambiguity with the min_amount parameter rather than explaining their interaction.

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 resource (AI funding rounds) and its scope ($25M+, lead investors, confirmed valuations, sources), so an agent knows this returns curated funding-round data rather than prices. It is clear enough to separate from the price-oriented siblings, though the verb/action itself is left implicit (the name carries 'get').

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: the $25M+ threshold and 'confirmed valuations' phrasing tell the agent this is a curated subset, not a full dataset. There is no explicit when-to-use/when-not guidance and no routing to alternatives, though the sibling tools cover a different domain so the cost of that omission is lower.

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