Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

bp_narratif

Read-only

Business Plan narratif — Gapup agent-payable C-suite expertise (CFO). Returns a structured, audited deliverable. Reference case: Stripe Series A 2012. 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.
raiseYes
companyYes
keyMetricsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changed
    • addedInput schema / properties / company / properties
      Added value: +{
+  "countryHQ": {
+    "maxLength": 60,
+    "minLength": 2,
+    "type": "string"
+  },
+  "foundedYear": {
+    "maximum": 2030,
+    "minimum": 1990,
+    "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"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "pitch",
+  "foundedYear",
+  "stage",
+  "countryHQ"
+]
    • addedInput schema / properties / keyMetrics / items
      Added value: +{
+  "maxLength": 80,
+  "minLength": 2,
+  "type": "string"
+}
    • addedInput schema / properties / keyMetrics / maxItems
      Added value: +6
    • addedInput schema / properties / keyMetrics / minItems
      Added value: +2
    • addedInput schema / properties / raise / properties
      Added value: +{
+  "investorAudience": {
+    "enum": [
+      "bank",
+      "vc",
+      "public-grant",
+      "mixed"
+    ],
+    "type": "string"
+  },
+  "targetAmountEur": {
+    "minimum": 50000,
+    "type": "integer"
+  },
+  "timelineMonths": {
+    "maximum": 24,
+    "minimum": 1,
+    "type": "integer"
+  }
+}
    • addedInput schema / properties / raise / required
      Added value: +[
+  "targetAmountEur",
+  "investorAudience",
+  "timelineMonths"
+]
    • addedInput schema / required
      Added value: +[
+  "company",
+  "raise",
+  "keyMetrics"
+]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds that it returns a structured, audited deliverable and that inputs are validated server-side, which provides some additional context beyond annotations.

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 concise with two sentences and a reference case. Every sentence adds information, though the reference case could be considered secondary. Front-loaded with the tool's purpose.

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?

Given the complexity (nested objects, no output schema, 4 parameters), the description is too minimal. It lacks details on return format, execution time, and how to use the async parameter. Despite a large sibling list, it offers no help in tool selection.

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 no parameter-specific meaning. It does not explain the required fields (company, raise, keyMetrics) beyond the schema constraints.

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 a narrative business plan with CFO-level expertise, naming the verb 'Returns' and referencing a specific case (Stripe Series A 2012). However, it does not differentiate from sibling tools like ftg_business_plan or financial_model_3statement.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description only says to 'send the documented case fields' but does not specify when not to use it or point to other tools.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially in competitive intelligence, ESG, and risk assessment. For example, there are multiple tools for competitor analysis (competitive_deep_dive, competitor_intel, competitor_moves, etc.) with unclear boundaries. Agents would struggle to select the correct tool without deep understanding of subtle differences.

Naming Consistency2/5

Tool names are a mix of English and French, and follow no consistent pattern. Some use snake_case (e.g., abm_architect, action_plan_esg), while others are verb-focused (e.g., content_catalog, fx_rate). The lack of a uniform naming convention makes it hard for agents to predict tool names.

Tool Count1/5

With 271 tools, the server is excessively large. Even for a broad knowledge domain, this number of tools makes discovery and selection inefficient. Typical coherent servers have 3-15 tools; this has an order of magnitude more, indicating poor scoping.

Completeness3/5

The tool set covers many domains (compliance, finance, marketing, HR, etc.), but the coverage is uneven due to redundancy. Key areas have multiple overlapping tools, while some sub-domains may still have gaps. Overall, the surface is broad but not well-curated.

Resources