Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

working_capital

Read-only

Optimiseur du BFR — Gapup agent-payable C-suite expertise (CFO). Returns a structured, audited deliverable. Reference case: Agicap — BFR optimisation · DSO 52→38j · Cash libéré +€2.8M · 3 quick wins immédiats. 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
industryNo
challengesYes
financialsYes
topCustomersNo
topSuppliersNo

Schema Changelog

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

  1. Changed16 schema fields changed
    • addedInput schema / properties / challenges / items
      Added value: +{
+  "maxLength": 300,
+  "minLength": 5,
+  "type": "string"
+}
    • addedInput schema / properties / challenges / maxItems
      Added value: +5
    • addedInput schema / properties / challenges / minItems
      Added value: +1
    • addedInput schema / properties / company / properties
      Added value: +{
+  "name": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  },
+  "stage": {
+    "enum": [
+      "pre-seed",
+      "seed",
+      "serie-a",
+      "serie-b",
+      "serie-c",
+      "serie-d-plus",
+      "profitable-sme",
+      "enterprise"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector",
+  "stage"
+]
    • addedInput schema / properties / financials / properties
      Added value: +{
+  "accountsPayableEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "accountsReceivableEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "annualRevenueEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "currentCashEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "currentDioDays": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "currentDpoDays": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "currentDsoDays": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "inventoryEur": {
+    "minimum": 0,
+    "type": "number"
+  }
+}
    • addedInput schema / properties / financials / required
      Added value: +[
+  "annualRevenueEur",
+  "currentCashEur",
+  "accountsReceivableEur",
+  "accountsPayableEur",
+  "currentDsoDays",
+  "currentDpoDays"
+]
    • addedInput schema / properties / industry / maxLength
      Added value: +100
    • addedInput schema / properties / industry / minLength
      Added value: +2
    • addedInput schema / properties / topCustomers / items
      Added value: +{
+  "maxLength": 100,
+  "type": "string"
+}
    • addedInput schema / properties / topCustomers / maxItems
      Added value: +5
    • addedInput schema / properties / topCustomers / minItems
      Added value: +0
    • addedInput schema / properties / topSuppliers / items
      Added value: +{
+  "maxLength": 100,
+  "type": "string"
+}
    • addedInput schema / properties / topSuppliers / maxItems
      Added value: +5
    • addedInput schema / properties / topSuppliers / minItems
      Added value: +0
    • addedInput schema / required
      Added value: +[
+  "company",
+  "financials",
+  "challenges"
+]
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true. The description adds that inputs are validated server-side, which is common, and does not contradict annotations. However, it does not elaborate on behavioral traits like side effects, authorization, or latency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but includes marketing fluff (e.g., 'Gapup agent-payable C-suite expertise (CFO)', reference case). While front-loaded with purpose, it could be more concise and direct.

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 7 parameters, nested objects, no output schema, the description lacks essential context. It does not describe the deliverable's structure, success conditions, or how to interpret the output, leaving significant gaps for an agent.

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 14% (low). The description does not explain any parameters beyond saying 'send the documented case fields', providing no added semantics. Parameters have minimal schema descriptions, but the tool description should compensate for low coverage, which it fails to do.

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 states it is a 'BFR Optimizer' for CFO-level working capital optimization, which is clear. It mentions returning a structured deliverable and provides a reference case. However, it does not explicitly differentiate from sibling tools like 'working_capital_esg_impact_rater' or 'treasury_optimizer'.

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 explicit guidance on when to use this tool versus alternatives. The description references CFO expertise and a case study, but does not state prerequisites, exclusions, or when not to use it.

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