Skip to main content
Glama

mcp-knowledge

by io.github.getgapup
OverviewDiscussionsAdmin

investor_list

Read-only

Liste d'investisseurs + warm intros — Gapup agent-payable C-suite expertise (FUNDRAISING). Returns a structured, audited deliverable. Reference case: Agicap Série D — 25 VCs matchés · Tier A: Balderton/Accel/Partech · Warm intro path chaque investisseur. Inputs are validated server-side — send the documented case fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asyncNoIf true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client timeouts.
roundYes
companyYes
existingInvestorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / company / properties
      Added value: +{
+  "name": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector"
+]
    • addedInput schema / properties / existingInvestors / items
      Added value: +{
+  "maxLength": 100,
+  "type": "string"
+}
    • addedInput schema / properties / existingInvestors / maxItems
      Added value: +5
    • addedInput schema / properties / existingInvestors / minItems
      Added value: +0
    • addedInput schema / properties / round / properties
      Added value: +{
+  "arrCurrent": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "geography": {
+    "items": {
+      "maxLength": 50,
+      "type": "string"
+    },
+    "maxItems": 5,
+    "minItems": 1,
+    "type": "array"
+  },
+  "stage": {
+    "enum": [
+      "pre-seed",
+      "seed",
+      "series-a",
+      "series-b",
+      "series-c",
+      "growth",
+      "pre-ipo"
+    ],
+    "type": "string"
+  },
+  "ticketSizeMax": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "ticketSizeMin": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "useCase": {
+    "maxLength": 300,
+    "minLength": 10,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / round / required
      Added value: +[
+  "stage",
+  "ticketSizeMin",
+  "ticketSizeMax",
+  "geography",
+  "useCase"
+]
    • addedInput schema / required
      Added value: +[
+  "company",
+  "round"
+]
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, and the description adds useful context: the tool returns an audited deliverable, includes warm intro paths, and validates inputs server-side. This goes beyond the annotations without contradicting them.

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?

The description is compact and front-loaded with the core purpose. The reference case adds some promotional noise but is brief and arguably helpful for context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and complex nested parameters, the description should explain the deliverable's contents more concretely. Saying 'structured, audited deliverable' is vague, and the async parameter is not mentioned at all.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% and the description adds almost no detail about the parameters. It only references 'documented case fields' without explaining what they are, leaving the nested company/round/existingInvestors structures largely undocumented.

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 clearly states the tool produces an investor list with warm intros and a structured, audited deliverable, and provides a concrete reference case. However, it doesn't explicitly differentiate itself from similar siblings like investor_shortlist.

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

Usage Guidelines4/5

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

The description gives clear context: it's for FUNDRAISING and investor warm intros, and it instructs to send the documented case fields. It does not mention alternatives or when not to use it, but the intended use is clear enough.

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

All mcp-knowledge 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