Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

ai_governance_pilot

Read-only

Pilotage de gouvernance IA — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Reference case: TalentScope SAS — scoring IA candidats RH (EU AI Act Annex III §4, high-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.
focusNo
companyYes
aiUseCasesYes
targetFrameworksYes

Schema Changelog

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

  1. Changed10 schema fields changed
    • addedInput schema / properties / aiUseCases / items
      Added value: +{
+  "properties": {
+    "dataTypes": {
+      "items": {
+        "type": "string"
+      },
+      "maxItems": 10,
+      "type": "array"
+    },
+    "description": {
+      "maxLength": 500,
+      "type": "string"
+    },
+    "impactedUsers": {
+      "maxLength": 200,
+      "type": "string"
+    },
+    "name": {
+      "maxLength": 200,
+      "minLength": 2,
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "description",
+    "dataTypes",
+    "impactedUsers"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / aiUseCases / maxItems
      Added value: +20
    • addedInput schema / properties / aiUseCases / minItems
      Added value: +1
    • addedInput schema / properties / company / properties
      Added value: +{
+  "country": {
+    "maxLength": 80,
+    "minLength": 2,
+    "type": "string"
+  },
+  "fte": {
+    "minimum": 1,
+    "type": "integer"
+  },
+  "jurisdictions": {
+    "items": {
+      "enum": [
+        "FR",
+        "EU",
+        "UK",
+        "US-CA",
+        "other"
+      ],
+      "type": "string"
+    },
+    "maxItems": 5,
+    "minItems": 1,
+    "type": "array"
+  },
+  "name": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "revenueEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "sector": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector",
+  "fte",
+  "revenueEur",
+  "country",
+  "jurisdictions"
+]
    • addedInput schema / properties / focus / maxLength
      Added value: +500
    • addedInput schema / properties / targetFrameworks / items
      Added value: +{
+  "enum": [
+    "EU AI Act",
+    "ISO 42001",
+    "NIST AI RMF",
+    "GDPR Art.22",
+    "HIPAA",
+    "AGIRC-ARRCO",
+    "UK AI Code"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / targetFrameworks / maxItems
      Added value: +7
    • addedInput schema / properties / targetFrameworks / minItems
      Added value: +1
    • addedInput schema / required
      Added value: +[
+  "company",
+  "aiUseCases",
+  "targetFrameworks"
+]
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds context about returning a structured, audited deliverable and gives a reference case, which is helpful but does not detail side effects, authorization needs, or rate limits. It does not contradict annotations.

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 brief (two sentences) but contains a typo ('Gapup') and uses technical jargon without clarification. While concise, it sacrifices clarity and could be better structured with a clear action verb and resource scope.

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 complexity of AI governance with nested input objects and no output schema, the description falls short. It does not specify what the deliverable contains, how to interpret the output, or how this pilot differs from the full report sibling. The reference case helps but is insufficient.

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 low (20% - only 'async' has a description). The description does not explain the purpose or format of the key nested parameters like 'company', 'aiUseCases', or 'targetFrameworks', leaving the agent to infer from the schema alone.

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 performs 'Pilotage de gouvernance IA' and returns a structured audited deliverable, with a concrete reference case. However, it could better distinguish from the sibling 'ai_governance_full_report_async' which likely performs a similar but more comprehensive function.

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?

The description mentions inputs are validated server-side but provides no guidance on when to use this tool versus alternatives like the full governance report or other governance-focused tools in the sibling list. There is no when-to-use or when-not-to-use advice.

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