Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

churn_defender

Read-only

Bouclier anti-churn — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Spendesk — portefeuille 400 clients PME/ETI, détection churn Q2 2025 (€8M ARR). 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
accountsYes
csrContextNo
analysisWindowDaysYes

Schema Changelog

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

  1. Changed11 schema fields changed
    • addedInput schema / properties / accounts / items
      Added value: +{
+  "properties": {
+    "arrEur": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "championsLeft": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "competitorMentions": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "contractRenewalDate": {
+      "type": "string"
+    },
+    "csmOwner": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "industry": {
+      "type": "string"
+    },
+    "lastLoginDaysAgo": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "missedPayments": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    },
+    "notes": {
+      "maxLength": 500,
+      "type": "string"
+    },
+    "npsScore": {
+      "maximum": 100,
+      "minimum": -100,
+      "type": "number"
+    },
+    "openTickets": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "size": {
+      "enum": [
+        "startup",
+        "sme",
+        "mid-market",
+        "enterprise"
+      ],
+      "type": "string"
+    },
+    "usageDropPct": {
+      "maximum": 100,
+      "minimum": -100,
+      "type": "number"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "arrEur",
+    "contractRenewalDate",
+    "industry",
+    "size",
+    "csmOwner"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / accounts / maxItems
      Added value: +30
    • addedInput schema / properties / accounts / minItems
      Added value: +5
    • addedInput schema / properties / analysisWindowDays / default
      Added value: +90
    • addedInput schema / properties / analysisWindowDays / maximum
      Added value: +180
    • addedInput schema / properties / analysisWindowDays / minimum
      Added value: +30
    • changedInput schema / properties / analysisWindowDays / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / company / properties
      Added value: +{
+  "arr": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "avgContractValueEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "currentChurnRatePct": {
+    "maximum": 100,
+    "minimum": 0,
+    "type": "number"
+  },
+  "name": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "renewalWindowMonths": {
+    "maximum": 12,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "sector": {
+    "maxLength": 160,
+    "minLength": 2,
+    "type": "string"
+  },
+  "targetChurnRatePct": {
+    "maximum": 100,
+    "minimum": 0,
+    "type": "number"
+  },
+  "totalAccounts": {
+    "minimum": 1,
+    "type": "integer"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector",
+  "arr",
+  "totalAccounts",
+  "avgContractValueEur",
+  "currentChurnRatePct",
+  "targetChurnRatePct",
+  "renewalWindowMonths"
+]
    • addedInput schema / properties / csrContext / maxLength
      Added value: +800
    • addedInput schema / required
      Added value: +[
+  "company",
+  "accounts",
+  "analysisWindowDays"
+]
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that the tool returns a deliverable and validates inputs server-side, which is consistent but does not reveal additional behaviors (e.g., expected processing time, output structure). No contradiction found.

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 concise (three sentences) but includes a tangential reference case. It front-loads the purpose but could be more efficient by removing the example and focusing on functionality.

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 tool's complexity (many nested parameters, no output schema), the description is insufficient. It omits details about the deliverable's format, how results are used, and any post-processing steps, leaving significant gaps for the 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?

With only 20% schema description coverage, the description should compensate but does not explain any parameters. It only says 'send the documented case fields', leaving the meaning of complex nested objects (company, accounts) undcribed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is an anti-churn tool that returns a structured audited deliverable, but lacks a specific verb (e.g., 'analyze' or 'generate') and does not clearly distinguish from siblings like 'champion_mapping' or 'renewal_optimizer'. The reference case provides context but the purpose remains somewhat vague.

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 mention of server-side validation and 'send the documented case fields' implies a usage requirement but does not specify scenarios or exclude inappropriate uses.

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