gapup-mcp

operational_dashboards

Read-only

Dashboards opérationnels — Gapup agent-payable C-suite expertise (COO). Returns a structured, audited deliverable. Reference case: Qonto (5 départements · 12 KPIs) — 4 dashboards live en 3 semaines · time-to-décision -55%. Inputs are validated server-side — send the documented case fields.

Input Schema

TableJSON Schema

Name	Required	Description
`async`	No	If 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.
`company`	Yes
`techStack`	Yes
`departments`	Yes
`kpiRequests`	Yes
`primaryDashboardTool`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedJun 4, 2026

addedInput schema / properties / company / properties

Added value: +{
+  "name": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  }
+}

addedInput schema / properties / company / required
```
Added value: +[
+  "name",
+  "sector"
+]
```
removedInput schema / properties / currentToolsLandscape
```
Removed value: -{
-  "type": "object"
-}
```

addedInput schema / properties / departments / items

Added value: +{
+  "maxLength": 60,
+  "type": "string"
+}

addedInput schema / properties / departments / maxItems
```
Added value: +8
```
addedInput schema / properties / departments / minItems
```
Added value: +1
```
removedInput schema / properties / implementationConstraints
```
Removed value: -{
-  "type": "array"
-}
```

addedInput schema / properties / kpiRequests

Added value: +{
+  "items": {
+    "properties": {
+      "currentTrackingMethod": {
+        "enum": [
+          "manual",
+          "spreadsheet",
+          "partial-tool",
+          "none"
+        ],
+        "type": "string"
+      },
+      "department": {
+        "maxLength": 60,
+        "minLength": 2,
+        "type": "string"
+      },
+      "frequency": {
+        "enum": [
+          "realtime",
+          "daily",
+          "weekly",
+          "monthly"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "maxLength": 100,
+        "minLength": 2,
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "department",
+      "currentTrackingMethod",
+      "frequency"
+    ],
+    "type": "object"
+  },
+  "maxItems": 12,
+  "minItems": 3,
+  "type": "array"
+}

removedInput schema / properties / objectives
```
Removed value: -{
-  "type": "array"
-}
```

addedInput schema / properties / primaryDashboardTool

Added value: +{
+  "enum": [
+    "metabase",
+    "tableau",
+    "powerbi",
+    "looker",
+    "grafana",
+    "notion",
+    "other",
+    "none"
+  ],
+  "type": "string"
+}

addedInput schema / properties / techStack

Added value: +{
+  "items": {
+    "maxLength": 60,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "minItems": 0,
+  "type": "array"
+}

addedInput schema / required

Added value: +[
+  "company",
+  "departments",
+  "kpiRequests",
+  "techStack"
+]

First observedMay 25, 2026

TDQS

C2.6/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 server-side validation and an 'audited deliverable', which is consistent and adds some context. However, no mention of rate limits, required permissions, or output format, so it's adequate but not rich.

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 relatively short and front-loaded with the tool name, but it includes promotional content (reference case, time-to-decision metric) that isn't essential. The core behavioral information is present but mixed with marketing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and the description gives only a vague 'structured, audited deliverable' without format details. It doesn't mention the async option or required fields, leaving a complex 6-parameter tool under-specified for an agent.

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%, and the description merely says 'send the documented case fields' without listing or explaining any parameters. With 6 parameters including nested objects, the agent gets no help understanding what to send.

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?

Description identifies an operational dashboard deliverable for C-suite/COO, illustrated by the Qonto reference case. However, it lacks an explicit verb like 'generates' or 'creates', relying on 'Returns' to imply production, so it's not fully clear as a one-liner.

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 over sibling dashboard tools (e.g., marketing_roi_dashboard). The only hint is 'C-suite expertise (COO)' and the operational focus, but there are no exclusions or explicit alternative comparisons.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All gapup-mcp tools Inspect

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

Need Help?