Skip to main content
Glama

gapup-mcp

by io.gapup.mcp
OverviewDiscussionsAdmin

strategic_options_analyzer

Read-only

Analyseur d'options stratégiques — Gapup agent-payable C-suite expertise (CSO). Returns a structured, audited deliverable. Reference case: Aircall — 5 options stratégiques post-Série D (2023-2024). 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.
companyYes
optionHypothesesYes
strategicContextYes
founderConstraintsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / company / properties
      Added value: +{
+  "countryHQ": {
+    "maxLength": 60,
+    "minLength": 2,
+    "type": "string"
+  },
+  "currentArrEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "foundedYear": {
+    "maximum": 2030,
+    "minimum": 1990,
+    "type": "integer"
+  },
+  "headcountNow": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "name": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "pitch": {
+    "maxLength": 800,
+    "minLength": 20,
+    "type": "string"
+  },
+  "stage": {
+    "enum": [
+      "pre-seed",
+      "seed",
+      "series-a",
+      "series-b",
+      "series-c",
+      "growth",
+      "public"
+    ],
+    "type": "string"
+  },
+  "url": {
+    "format": "uri",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "pitch",
+  "stage",
+  "countryHQ",
+  "foundedYear",
+  "currentArrEur",
+  "headcountNow"
+]
    • addedInput schema / properties / founderConstraints / properties
      Added value: +{
+  "maxCashRequiredEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "maxDilutionPct": {
+    "maximum": 100,
+    "minimum": 0,
+    "type": "number"
+  },
+  "mustRetainControl": {
+    "type": "boolean"
+  },
+  "noGoConditions": {
+    "items": {
+      "maxLength": 200,
+      "minLength": 5,
+      "type": "string"
+    },
+    "maxItems": 5,
+    "type": "array"
+  },
+  "timeToFirstValidationWeeks": {
+    "maximum": 52,
+    "minimum": 4,
+    "type": "integer"
+  }
+}
    • addedInput schema / properties / founderConstraints / required
      Added value: +[
+  "maxCashRequiredEur",
+  "maxDilutionPct",
+  "mustRetainControl",
+  "timeToFirstValidationWeeks"
+]
    • addedInput schema / properties / optionHypotheses / items
      Added value: +{
+  "properties": {
+    "hypothesis": {
+      "maxLength": 400,
+      "minLength": 20,
+      "type": "string"
+    },
+    "id": {
+      "maxLength": 60,
+      "minLength": 2,
+      "type": "string"
+    },
+    "label": {
+      "maxLength": 120,
+      "minLength": 5,
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "label",
+    "hypothesis"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / optionHypotheses / maxItems
      Added value: +6
    • addedInput schema / properties / optionHypotheses / minItems
      Added value: +3
    • addedInput schema / properties / strategicContext / properties
      Added value: +{
+  "burnMonthlyEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "cashEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "cashRunwayMonths": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "coreCompetencies": {
+    "items": {
+      "maxLength": 200,
+      "minLength": 5,
+      "type": "string"
+    },
+    "maxItems": 6,
+    "minItems": 2,
+    "type": "array"
+  },
+  "triggerEvent": {
+    "maxLength": 500,
+    "minLength": 20,
+    "type": "string"
+  },
+  "windowOpportunityMonths": {
+    "maximum": 36,
+    "minimum": 3,
+    "type": "integer"
+  }
+}
    • addedInput schema / properties / strategicContext / required
      Added value: +[
+  "triggerEvent",
+  "windowOpportunityMonths",
+  "cashRunwayMonths",
+  "cashEur",
+  "burnMonthlyEur",
+  "coreCompetencies"
+]
    • addedInput schema / required
      Added value: +[
+  "company",
+  "strategicContext",
+  "optionHypotheses",
+  "founderConstraints"
+]
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint and openWorldHint. The description adds that the tool returns a structured, audited deliverable and that inputs are validated server-side, which is useful. However, it does not explain what 'audited' entails, potential processing time (beyond async), or any other behavioral traits.

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?

Three sentences, front-loaded with the tool's purpose. The phrase 'Gapup agent-payable C-suite expertise (CSO)' is somewhat vague and unnecessary, but overall the description is efficient and avoids redundancy.

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?

Despite the tool's high complexity (4 required nested objects, no output schema), the description provides minimal context. It does not outline the analysis workflow, the nature of the deliverable beyond 'structured, audited,' or any prerequisites. The reference case helps but is not sufficient for such a sophisticated tool.

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 20%, and the description does not explain any of the parameters. It merely says 'send the documented case fields,' which adds no semantic meaning beyond the schema's sparse property names. The nested objects (company, strategicContext, optionHypotheses, founderConstraints) remain superficially defined.

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 name and description clearly indicate the tool analyzes strategic options and returns a structured, audited deliverable, with a concrete reference case (Aircall post-Series D). However, it does not distinguish itself from sibling strategy tools like growth_path_architect or market_entry_strategist.

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?

The description implies use for C-suite strategic decision-making ('C-suite expertise (CSO)') and provides an example, but gives no explicit guidance on when to choose this over alternatives or when not to use it. No exclusion criteria are mentioned.

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

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