Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

internal_communication

Read-only

Communication interne — Gapup agent-payable C-suite expertise (CHRO). Returns a structured, audited deliverable. Reference case: Cas démo — Communication interne. 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
contextYes
audienceSegmentsYes

Schema Changelog

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

  1. Changed9 schema fields changed
    • addedInput schema / properties / audienceSegments / items
      Added value: +{
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "notes": {
+      "maxLength": 200,
+      "type": "string"
+    },
+    "size": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "name",
+    "size"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / audienceSegments / maxItems
      Added value: +8
    • addedInput schema / properties / audienceSegments / minItems
      Added value: +2
    • addedInput schema / properties / company / properties
      Added value: +{
+  "fte": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "geographies": {
+    "items": {
+      "maxLength": 60,
+      "minLength": 2,
+      "type": "string"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  },
+  "name": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "nbSites": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "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 / context / properties
      Added value: +{
+  "currentMaturity": {
+    "type": "string"
+  },
+  "knownGaps": {
+    "items": {
+      "maxLength": 200,
+      "minLength": 5,
+      "type": "string"
+    },
+    "maxItems": 8,
+    "minItems": 1,
+    "type": "array"
+  },
+  "upcomingChanges": {
+    "items": {
+      "maxLength": 200,
+      "minLength": 5,
+      "type": "string"
+    },
+    "maxItems": 8,
+    "type": "array"
+  },
+  "voiceTone": {
+    "maxLength": 200,
+    "minLength": 5,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / context / required
      Added value: +[
+  "currentMaturity",
+  "knownGaps",
+  "voiceTone"
+]
    • addedInput schema / properties / focus / maxLength
      Added value: +400
    • addedInput schema / required
      Added value: +[
+  "company",
+  "context",
+  "audienceSegments"
+]
  2. First observed

TDQS

C2.2/5.0
Behavior3/5

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

The description adds that the tool returns a structured, audited deliverable and that inputs are validated server-side. Annotations already indicate readOnlyHint=true and openWorldHint=true, so the description does not contradict but adds limited behavioral context. No details on output format or performance characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but not well-structured. It begins with a French phrase and uses unclear jargon, wasting the opening sentence. The key information (returns deliverable) is present but could be stated more directly.

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?

Given the tool has nested objects and no output schema, the description should compensate with details about output format or behavior. It does not explain what the deliverable contains, how to interpret results, or provide examples. The description is inadequate for a complex tool.

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 20%, but the description provides no information about parameters beyond 'send the documented case fields.' It fails to explain the meaning or usage of any parameters, leaving the agent with insufficient guidance.

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

Purpose3/5

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

The description states it returns a structured, audited deliverable for internal communication, providing a general sense of purpose. However, it uses jargon ('Gapup agent-payable C-suite expertise (CHRO)') without clear explanation, and the verb 'returns' is implicit. It does not clearly differentiate from siblings, though siblings are numerous and none directly duplicate this 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?

No guidance on when to use this tool versus alternatives. The description only mentions server-side validation and to send documented case fields, but does not provide context for decision-making or exclusions.

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