Skip to main content
Glama

Match startup to funds

match_startup
Read-onlyIdempotent

ALTERNATIVE ENTRY POINT when you do not know what to search for. Describe a startup in plain language and receive the top 10 matching funds, each with a slug, a reason and a score. Use this instead of search_funds when the brief is qualitative ('climate hardware, pre-seed, Europe') rather than a filter. Slower than the other tools, three to ten seconds, because it reasons over every tracked fund: allow for that before you time out and retry. COST: included in Pro, or €0.25 per call over MPP if you have no key. Cost: included in Pro; otherwise EUR 0.25 per call (25 credits) on an agent key, or the same amount paid inline over MPP with no key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "description": "<description>"
    },
    "name": "match_startup"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNoFunding stage. Must be one of the listed enum values; common spellings are normalised.
regionNoOptional region. A soft boost for funds headquartered in, or declaring a focus on, that region; never excludes a fund.
countryNoStartup HQ country, spelled out in full. A soft boost for funds headquartered there, not a hard filter.
descriptionYesStartup description (max 500 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country, spelled out in full"New value: +"Startup HQ country, spelled out in full. A soft boost for funds headquartered there, not a hard filter."
    • addedInput schema / properties / region
      Added value: +{
      +  "description": "Optional region. A soft boost for funds headquartered in, or declaring a focus on, that region; never excludes a fund.",
      +  "enum": [
      +    "DACH",
      +    "EU",
      +    "Nordics",
      +    "UK",
      +    "US"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / stage / description
      Previous value: -"Funding stage. Must be one of the listed enum values."New value: +"Funding stage. Must be one of the listed enum values; common spellings are normalised."
  3. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country"New value: +"Country, spelled out in full"
    • changedInput schema / properties / stage / description
      Previous value: -"Funding stage"New value: +"Funding stage. Must be one of the listed enum values."
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish a safe, read-only, idempotent operation, and the description adds real context beyond them: result cardinality (top 10), latency (three to ten seconds because it reasons over every tracked fund), and the warning not to time out and retry. It also discloses the full cost model (Pro included, €0.25/call via agent key or inline MPP).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening and the search_funds routing sentence are well front-loaded and earn their place, but the pricing is stated twice in near-identical form ('COST: included in Pro, or €0.25 per call over MPP if you have no key' followed by 'Cost: included in Pro; otherwise EUR 0.25 per call (25 credits)...'). That duplicated sentence wastes space in an otherwise tight definition.

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?

There is no output schema, but the description compensates by describing the return shape (top 10 funds with slug, reason, score). Combined with latency and cost disclosure, an agent has everything needed to call this correctly and set expectations.

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% and the schema already explains the soft-boost semantics of region and country and the enum constraint on stage. The description only reinforces the free-form nature of the `description` parameter via the qualitative-brief framing, adding little that the schema does not already say, so the baseline of 3 applies.

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 concrete action (describe a startup in plain language) with a concrete deliverable (top 10 matching funds, each with slug, reason and score). It also explicitly distinguishes itself from the sibling search_funds, so an agent can choose between them without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: use this instead of search_funds when the brief is qualitative ('climate hardware, pre-seed, Europe') rather than a filter. That names both the alternative and the deciding condition, and frames the tool as an entry point for the unknown-query case.

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.