Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

diversity_inclusion_metrics

Read-only

Métriques diversité & inclusion — Gapup agent-payable C-suite expertise (SUSTAINABILITY). Returns a structured, audited deliverable. Reference case: Cas démo — Métriques diversité & inclusion. 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
ambitionsYes
currentStateYes
regulatoryContextNo

Schema Changelog

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

  1. Changed10 schema fields changed
    • addedInput schema / properties / ambitions / maxLength
      Added value: +500
    • addedInput schema / properties / ambitions / minLength
      Added value: +15
    • addedInput schema / properties / company / properties
      Added value: +{
+  "fte": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "geographies": {
+    "items": {
+      "maxLength": 60,
+      "minLength": 2,
+      "type": "string"
+    },
+    "maxItems": 12,
+    "minItems": 1,
+    "type": "array"
+  },
+  "name": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 80,
+    "minLength": 2,
+    "type": "string"
+  },
+  "stage": {
+    "maxLength": 40,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector",
+  "fte",
+  "stage"
+]
    • addedInput schema / properties / currentState / properties
      Added value: +{
+  "ergCount": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "genderRepresentationPct": {
+    "properties": {
+      "exec": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "number"
+      },
+      "management": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "number"
+      },
+      "overall": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "overall",
+      "management",
+      "exec"
+    ],
+    "type": "object"
+  },
+  "knownChallenges": {
+    "items": {
+      "maxLength": 200,
+      "minLength": 5,
+      "type": "string"
+    },
+    "maxItems": 8,
+    "minItems": 1,
+    "type": "array"
+  },
+  "nationalityCount": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "payEquityGapPct": {
+    "type": "number"
+  }
+}
    • addedInput schema / properties / currentState / required
      Added value: +[
+  "genderRepresentationPct",
+  "knownChallenges"
+]
    • addedInput schema / properties / focus / maxLength
      Added value: +400
    • addedInput schema / properties / regulatoryContext / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / regulatoryContext / maxItems
      Added value: +8
    • addedInput schema / required
      Added value: +[
+  "company",
+  "currentState",
+  "ambitions"
+]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to repeat that. It adds that inputs are validated server-side and the output is an 'audited deliverable', but fails to mention that the tool supports an async mode via the 'async' parameter, which is a notable behavioral gap.

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 very brief, consisting of two short sentences plus a reference. It is concise without wasted words, but the brevity sacrifices crucial guidance. It is front-loaded with the tool's purpose and output type.

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 (6 parameters, nested objects, optional async, no output schema), the description is severely incomplete. It does not explain how to use the async parameter, what the output structure is, or how to fill the nested objects like company and currentState. The reference to a demo case 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?

With only 17% schema description coverage and no parameter details in the description, the agent is left to guess the meaning of fields like 'focus', 'regulatoryContext', and nested objects. The vague phrase 'send the documented case fields' does not compensate for the lack of parameter documentation.

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 states that the tool returns a 'structured, audited deliverable' for diversity & inclusion metrics. This is clear about the resource and output nature, but lacks a precise action verb like 'generate' or 'compute'. It distinguishes from siblings via the specific D&I domain, though not explicitly.

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 is provided on when to use this tool versus alternatives. The description only says to 'send the documented case fields' but does not offer context about prerequisites, limitations, or comparison to similar tools in the extensive sibling list.

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