Skip to main content
Glama
Sign In
Andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find investors who fit

get_thesis_match

Identifies up to three venture capital firms actively investing in companies like yours at a given stage, each backed by sourced evidence and a link to the original page.

Instructions

Fundraising, not selling: use this when the person is raising money and asks which investors to talk to. Finds up to 3 VC firms investing now in companies like theirs, each with a recent deal or stated focus and a link to the page it came from (a live web search, about 30 seconds). Only firms with sourced evidence are returned. Paid. Check the price with quote before running.

Input Schema

NameRequiredDescriptionDefault
stageYesCurrent funding stage. Infer from context if mentioned.
quoteIdNoOptional: the quote_id from quote, to pay the quoted price (held for 30 minutes).
arrRangeNoCurrent ARR range (e.g., "$0-$500K", "$500K-$2M", "$2M-$10M"). Infer or ask.
verticalNoIndustry vertical (e.g., "AI/ML", "FinTech", "HealthTech", "SaaS"). Infer from product description.
idempotencyKeyNoOptional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.
maxAmountCentsNoOptional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.
productDescriptionYesWhat the company does and who it serves. Infer from conversation context if the user has already described their product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.9
    • addedInput schema / properties / idempotencyKey
      Added value: +{
+  "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.",
+  "type": "string"
+}
    • addedInput schema / properties / maxAmountCents
      Added value: +{
+  "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / quoteId
      Added value: +{
+  "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes).",
+  "type": "string"
+}
  2. First observedv1.4.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description goes well beyond them by disclosing that this is a live web search taking about 30 seconds, capped at 3 firms, that only evidence-backed firms are returned, and that the call is paid with a quote-first pricing gate. That is exactly the context an agent needs before spending the user's money.

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 usage decision before any mechanics, and nearly every clause carries information (result cap, evidence requirement, source link, latency, pricing). The parentheticals stack up in the second sentence, costing a little readability.

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?

With 7 parameters and no output schema, the description still conveys the return shape (up to 3 firms, each with a recent deal or stated focus plus a source URL), the latency, and the billing guardrails. Nothing an agent needs to call this correctly and safely is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining why quoteId exists (check price with quote first) and setting the expectation that stage/vertical/product info is inferred from conversation. It also bounds the result set to 3, which shapes how maxAmountCents should be reasoned about.

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 verb and resource — finds up to 3 VC firms actively investing in companies like the user's, each with sourced evidence — and frames it as 'fundraising, not selling', which separates it from the sales-facing siblings like discover_prospects and get_icp_fit_score. An agent can route to it without opening the schema.

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 trigger ('when the person is raising money and asks which investors to talk to') and an explicit exclusion ('not selling'). It also states the prerequisite workflow: check the price with quote before running, which maps to the quoteId parameter.

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

Deploy Server

Other Tools