Skip to main content
Glama

gapup-mcp

by io.gapup.mcp
OverviewDiscussionsAdmin

meddic_scoring

Read-only

Scoring MEDDIC du pipeline — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub — Pipeline 8 deals · €2.1M · MEDDIC score moyen 62/100 · 3 deals at-risk. 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.
dealsYes
companyYes
productYes
salesCycleNo
targetWinRateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / company / properties
      Added value: +{
+  "name": {
+    "maxLength": 100,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 100,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector"
+]
    • addedInput schema / properties / deals / items
      Added value: +{
+  "properties": {
+    "accountName": {
+      "maxLength": 100,
+      "type": "string"
+    },
+    "closeTargetDays": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "competitorPresent": {
+      "maxLength": 100,
+      "type": "string"
+    },
+    "dealValueEur": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "id": {
+      "maxLength": 20,
+      "type": "string"
+    },
+    "meddic": {
+      "items": {
+        "properties": {
+          "dimension": {
+            "enum": [
+              "metrics",
+              "economic-buyer",
+              "decision-criteria",
+              "decision-process",
+              "identify-pain",
+              "champion"
+            ],
+            "type": "string"
+          },
+          "evidence": {
+            "maxLength": 300,
+            "type": "string"
+          },
+          "gaps": {
+            "items": {
+              "type": "string"
+            },
+            "maxItems": 5,
+            "type": "array"
+          },
+          "nextActions": {
+            "items": {
+              "type": "string"
+            },
+            "maxItems": 4,
+            "type": "array"
+          },
+          "score": {
+            "maximum": 10,
+            "minimum": 0,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "dimension",
+          "score",
+          "evidence",
+          "gaps",
+          "nextActions"
+        ],
+        "type": "object"
+      },
+      "maxItems": 6,
+      "minItems": 1,
+      "type": "array"
+    },
+    "notes": {
+      "maxLength": 500,
+      "type": "string"
+    },
+    "stage": {
+      "enum": [
+        "prospecting",
+        "discovery",
+        "qualification",
+        "proposal",
+        "negotiation",
+        "closing"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "accountName",
+    "dealValueEur",
+    "stage",
+    "closeTargetDays",
+    "meddic"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / deals / maxItems
      Added value: +20
    • addedInput schema / properties / deals / minItems
      Added value: +1
    • addedInput schema / properties / product / properties
      Added value: +{
+  "avgDealValueEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "name": {
+    "maxLength": 100,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / product / required
      Added value: +[
+  "name"
+]
    • addedInput schema / properties / salesCycle / properties
      Added value: +{
+  "avgActualDays": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "targetDays": {
+    "minimum": 0,
+    "type": "integer"
+  }
+}
    • addedInput schema / properties / salesCycle / required
      Added value: +[
+  "targetDays"
+]
    • addedInput schema / properties / targetWinRate / maximum
      Added value: +100
    • addedInput schema / properties / targetWinRate / minimum
      Added value: +0
    • addedInput schema / required
      Added value: +[
+  "company",
+  "product",
+  "deals"
+]
  2. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds server-side validation and an audited deliverable, which are useful behavioral details beyond the annotations. No contradictions detected.

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 the purpose front-loaded. The reference case adds length but provides a concrete example without being verbose. Overall, each sentence contributes meaning.

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 a complex nested schema with 6 parameters and no output schema, the description is too sparse. It doesn't describe expected deal fields, scoring logic, or result format beyond 'structured deliverable.' The reference case hints at metrics but is insufficient for a tool of this complexity.

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

Parameters1/5

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

Schema description coverage is only 17% (async only). The description does not explain company, product, deals, salesCycle, or targetWinRate. It only vaguely says 'send the documented case fields,' providing almost no semantic value for the parameters.

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 scores the pipeline against the MEDDIC framework and returns a structured, audited deliverable. This is a specific verb+resource combination that distinguishes it from generic sales tools, though it doesn't explicitly name sibling alternatives.

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 context 'Gapup agent-payable C-suite expertise (CRO)' implies the tool is for MEDDIC scoring in sales pipelines, but there is no explicit when-to-use or alternatives guidance. The usage is implied rather than clearly delineated.

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