Skip to main content
Glama

gapup-mcp

by io.gapup.mcp
OverviewDiscussionsAdmin

deal_coach

Read-only

Coach de deal MEDDIC — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Datadog Enterprise deal Société Générale €1.2M ARR — coaching MEDDIC + escalation plays + 14 next actions. Inputs are validated server-side — send the documented case fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dealYes
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.
focusNo
knownContextYes
buyingCommitteeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / buyingCommittee / items
      Added value: +{
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "role": {
+      "enum": [
+        "champion",
+        "economic-buyer",
+        "user",
+        "influencer",
+        "blocker"
+      ],
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "title",
+    "role"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / buyingCommittee / maxItems
      Added value: +8
    • addedInput schema / properties / buyingCommittee / minItems
      Added value: +2
    • addedInput schema / properties / deal / properties
      Added value: +{
+  "accountName": {
+    "type": "string"
+  },
+  "amountEur": {
+    "type": "number"
+  },
+  "daysInStage": {
+    "type": "integer"
+  },
+  "expectedCloseDate": {
+    "type": "string"
+  },
+  "ownerRep": {
+    "type": "string"
+  },
+  "stage": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / deal / required
      Added value: +[
+  "accountName",
+  "amountEur",
+  "stage",
+  "daysInStage",
+  "expectedCloseDate",
+  "ownerRep"
+]
    • addedInput schema / properties / focus
      Added value: +{
+  "maxLength": 400,
+  "type": "string"
+}
    • addedInput schema / properties / knownContext / maxLength
      Added value: +800
    • addedInput schema / properties / knownContext / minLength
      Added value: +20
    • addedInput schema / required
      Added value: +[
+  "deal",
+  "buyingCommittee",
+  "knownContext"
+]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, and the description adds that it returns a structured, audited deliverable with coaching and next actions. It doesn't disclose rate limits or error behavior but is consistent with a read-only advisory tool.

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 relatively concise with three sentences, but the reference case adds length. It's still efficient and front-loaded.

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?

For a tool with no output schema and low schema coverage, the description lacks details on output structure, parameter meanings, and usage criteria. The reference case gives some context but doesn't complete the picture.

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 coverage is only 20% (async parameter has description). The description vaguely refers to 'documented case fields' without explaining what deal, buyingCommittee, or knownContext should contain. It fails to compensate for the sparse schema.

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

Purpose5/5

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

The description clearly identifies the tool as a MEDDIC deal coach providing C-suite expertise (CRO). It uses specific verbs ('coach', 'returns') and describes the deliverable, distinguishing it from analytics tools like meddic_scoring.

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 when-to-use or alternative guidance. The description mentions validated inputs but doesn't explain when to choose this over related tools like deal_structurer or meddic_scoring.

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