Skip to main content
Glama

StartupMKT — Startup Discovery & Marketplace

Latest startup funding (Funding Radar)

latest_funding

Latest entries from StartupMKT Funding Radar — verified startup funding rounds from funding news sources, refreshed daily. Returns exactly what the current feed holds; amounts and rounds are passed through, never generated.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries to return (1-50, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 real work: it discloses data provenance ('verified... from funding news sources'), freshness ('refreshed daily'), and a fidelity guarantee that amounts/rounds are passed through and never generated. It does not state read-only-ness explicitly or describe empty-feed/pagination behavior.

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 tight sentences with the resource, provenance and freshness all front-loaded. Nothing is wasted and no sentence merely restates the title.

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?

For a single-parameter feed tool with no annotations and no output schema, the description supplies provenance, refresh cadence and a no-generation guarantee, which is most of what an agent needs. It stops short of describing the shape of a returned entry (fields beyond amounts and rounds), which is the only remaining gap.

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?

Only one parameter exists and schema description coverage is 100% ('How many entries to return (1-50, default 10)'), so the schema fully documents it. The description adds no extra meaning about limit semantics or feed-window behavior; baseline 3 applies.

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+resource: latest entries from a named funding feed, scoped to 'verified startup funding rounds from funding news sources'. The resource is unmistakably different in kind from about/get_collection/search_collections/startups_for_sale, though no sibling is named to route the agent explicitly.

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?

There is no explicit when-to-use statement, no exclusion, and no alternative named. Usage is only implied by 'latest' and 'refreshed daily', which lets an agent infer this is the freshness-oriented feed rather than a search or collection tool.

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