Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

esrs_narrative_builder

Read-only

Architecte du narratif ESRS / CSRD — Gapup agent-payable C-suite expertise (SUSTAINABILITY). Returns a structured, audited deliverable. Reference case: L'Oréal France — narratif ESRS E1+E5 + S1 + G1 · CSRD reporting 2025-2026 · double-matérialité chiffrée. 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
scopeYes
companyYes
contextYes
presenterScriptNo

Schema Changelog

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

  1. Changed9 schema fields changed
    • addedInput schema / properties / company / properties
      Added value: +{
+  "fte": {
+    "minimum": 1,
+    "type": "integer"
+  },
+  "name": {
+    "type": "string"
+  },
+  "reportingYear": {
+    "minimum": 2024,
+    "type": "integer"
+  },
+  "revenueEur": {
+    "type": "number"
+  },
+  "sector": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector",
+  "fte",
+  "revenueEur",
+  "reportingYear"
+]
    • addedInput schema / properties / context / properties
      Added value: +{
+  "recentChanges": {
+    "maxLength": 500,
+    "type": "string"
+  },
+  "strategicCommitments": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 5,
+    "minItems": 1,
+    "type": "array"
+  }
+}
    • addedInput schema / properties / context / required
      Added value: +[
+  "strategicCommitments"
+]
    • addedInput schema / properties / focus / maxLength
      Added value: +400
    • addedInput schema / properties / presenterScript
      Added value: +{
+  "items": {
+    "properties": {
+      "durationSec": {
+        "maximum": 120,
+        "minimum": 15,
+        "type": "number"
+      },
+      "keyPointsToAcknowledge": {
+        "items": {
+          "maxLength": 200,
+          "minLength": 5,
+          "type": "string"
+        },
+        "maxItems": 5,
+        "type": "array"
+      },
+      "motionHint": {
+        "enum": [
+          "opening-confidence",
+          "explaining",
+          "pointing-at-chart",
+          "thoughtful-pause",
+          "emphatic-point",
+          "nodding-listening",
+          "hand-gesture-open",
+          "summary-pose",
+          "closing-confidence"
+        ],
+        "type": "string"
+      },
+      "narration": {
+        "maxLength": 1200,
+        "minLength": 80,
+        "type": "string"
+      },
+      "slideId": {
+        "maxLength": 60,
+        "minLength": 2,
+        "type": "string"
+      },
+      "slideTitle": {
+        "maxLength": 120,
+        "minLength": 3,
+        "type": "string"
+      }
+    },
+    "required": [
+      "slideId",
+      "slideTitle",
+      "narration",
+      "durationSec"
+    ],
+    "type": "object"
+  },
+  "maxItems": 15,
+  "minItems": 6,
+  "type": "array"
+}
    • addedInput schema / properties / scope / properties
      Added value: +{
+  "countriesOfOperation": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 15,
+    "minItems": 1,
+    "type": "array"
+  },
+  "standardsApplicable": {
+    "items": {
+      "enum": [
+        "ESRS-E1-climate",
+        "ESRS-E2-pollution",
+        "ESRS-E3-water",
+        "ESRS-E4-biodiversity",
+        "ESRS-E5-resources",
+        "ESRS-S1-workforce",
+        "ESRS-S2-value-chain",
+        "ESRS-S3-communities",
+        "ESRS-S4-consumers",
+        "ESRS-G1-business-conduct"
+      ],
+      "type": "string"
+    },
+    "maxItems": 10,
+    "minItems": 3,
+    "type": "array"
+  },
+  "valueChainScope": {
+    "maxLength": 500,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / scope / required
      Added value: +[
+  "standardsApplicable",
+  "countriesOfOperation",
+  "valueChainScope"
+]
    • addedInput schema / required
      Added value: +[
+  "company",
+  "scope",
+  "context"
+]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that inputs are validated server-side and returns a structured deliverable, providing some behavioral context beyond annotations without contradiction.

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 four sentences and front-loads the core purpose, though the reference case adds length without being essential.

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, no output schema, async parameter), the description omits key details like return structure, async handling, and parameter semantics, leaving significant gaps.

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 description coverage is only 17%. The description does not explain the parameters (company, scope, context) beyond 'send the documented case fields', failing to compensate for the low coverage.

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 it builds ESRS/CSRD narrative reports and returns a structured deliverable, with a reference case. However, it does not differentiate from sibling tools like sustainability_report or esg_audit_multi.

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 provides a reference case and mentions validated inputs, but offers no guidance on when to use this tool versus alternatives, nor when not to use it.

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