Skip to main content
Glama
Sign In

Andru

by io.github.geter-andru
OverviewDiscussionsAdmin

Find investors who fit

get_thesis_match

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.

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": {
      "productDescription": "<productDescription>",
      "stage": "<stage>"
    },
    "name": "get_thesis_match"
  }
}

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. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare openWorldHint=true and readOnlyHint=false, and the description corroborates this with 'a live web search, about 30 seconds' plus the evidence-only guarantee ('Only firms with sourced evidence are returned') and a hard result cap of 3. What is missing is the cost dimension: readOnlyHint=false is driven by this being a paid call (quoteId, maxAmountCents), and the description never mentions that the call charges money or consumes a quote, leaving the most consequential behavior to the schema.

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?

Three tight sentences, front-loaded with the usage trigger and a separator from the sales tools, then scope, then the evidence/latency contract. No sentence is filler and none repeats the schema verbatim.

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?

There is no output schema, yet the description still defines the return shape well: at most 3 firms, each with a recent deal or stated focus and a source URL. For a non-read-only, presumably paid tool, however, the pricing/quote flow and the ~30s wait expectation are only partly covered, so an agent could call it without knowing it incurs a charge.

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%, so every parameter (stage enum, productDescription, arrRange, vertical, quoteId, idempotencyKey, maxAmountCents) is already documented in structured form; baseline is 3. The description adds no field-level guidance beyond implying that the company profile comes from conversation context and that results are capped at 3.

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 VC firms) with explicit scope: up to 3 firms, actively investing now, in companies like theirs, each backed by a recent deal or stated focus plus a source link. The framing 'Fundraising, not selling' immediately separates it from the sales-oriented siblings (discover_prospects, get_icp_fit_score, get_messaging_framework).

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?

'Use this when the person is raising money and asks which investors to talk to' gives a concrete trigger, and 'Fundraising, not selling' is an explicit when-not that rules out the whole go-to-market/sales class of sibling tools. The agent does not need to infer the selection condition.

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

All Andru toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources