Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

cyber_risk_auditor

Read-only

Auditeur de risque cyber — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Reference case: Qonto — Audit cyber risque B2B FinTech · Score 58/100 → roadmap 90j · 8 findings critiques/high · économie prime -28%. 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
techStackYes
currentPostureYes

Schema Changelog

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

  1. Changed8 schema fields changed
    • addedInput schema / properties / company / properties
      Added value: +{
+  "dataTypes": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 6,
+    "minItems": 1,
+    "type": "array"
+  },
+  "name": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "size": {
+    "enum": [
+      "startup",
+      "sme",
+      "midmarket",
+      "enterprise"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector",
+  "size",
+  "dataTypes"
+]
    • addedInput schema / properties / currentPosture / properties
      Added value: +{
+  "hasPenTest": {
+    "type": "boolean"
+  },
+  "hasSOC": {
+    "type": "boolean"
+  },
+  "hasSOC2orISO27001": {
+    "type": "boolean"
+  },
+  "incidentPlanExists": {
+    "type": "boolean"
+  },
+  "mfa": {
+    "type": "boolean"
+  }
+}
    • addedInput schema / properties / currentPosture / required
      Added value: +[
+  "hasSOC",
+  "hasPenTest",
+  "hasSOC2orISO27001",
+  "mfa",
+  "incidentPlanExists"
+]
    • addedInput schema / properties / focus / maxLength
      Added value: +400
    • addedInput schema / properties / techStack / properties
      Added value: +{
+  "cloudProviders": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 5,
+    "minItems": 0,
+    "type": "array"
+  },
+  "endpointMgmt": {
+    "maxLength": 100,
+    "type": "string"
+  },
+  "identityProvider": {
+    "maxLength": 100,
+    "type": "string"
+  },
+  "keyApps": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 8,
+    "minItems": 0,
+    "type": "array"
+  }
+}
    • addedInput schema / properties / techStack / required
      Added value: +[
+  "cloudProviders",
+  "keyApps"
+]
    • addedInput schema / required
      Added value: +[
+  "company",
+  "techStack",
+  "currentPosture"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds context by stating it returns a 'structured, audited deliverable' and that inputs are validated server-side. No contradiction with annotations.

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 concise (4 sentences) and includes key elements, but the mixed use of French and English and the placement of the reference case could be better organized for clarity.

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 the nested input schema and lack of output schema, the description is too brief. It lacks details on the output format, how to use the 'focus' parameter, and examples beyond the single reference case.

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 20%, and the description does not explain the meaning or usage of individual parameters. The vague instruction 'send the documented case fields' fails to compensate for missing schema descriptions.

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

Purpose5/5

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

The description clearly states the tool performs a cyber risk audit and returns a structured deliverable. The reference case (Qonto) provides a concrete example, distinguishing it from sibling tools like audit_pre_flight 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for C-suite cyber risk assessment ('agent-payable C-suite expertise') but does not explicitly state when to use this tool versus alternatives, nor does it provide conditions for not using 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