Skip to main content
Glama

mcp-knowledge

by io.github.getgapup
OverviewDiscussionsAdmin

content_engine

Read-only

Moteur de contenu — Gapup agent-payable C-suite expertise (CMO). Returns a structured, audited deliverable. Reference case: Notion — content engine 2026 (productivity B2B). 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.
brandYes
monthsYes
clusterYes
maxArticlesPerMonthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / brand / properties
      Added value: +{
+  "audienceLabel": {
+    "maxLength": 200,
+    "minLength": 5,
+    "type": "string"
+  },
+  "name": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "voiceAttributes": {
+    "items": {
+      "maxLength": 40,
+      "minLength": 2,
+      "type": "string"
+    },
+    "maxItems": 5,
+    "minItems": 2,
+    "type": "array"
+  }
+}
    • addedInput schema / properties / brand / required
      Added value: +[
+  "name",
+  "voiceAttributes",
+  "audienceLabel"
+]
    • addedInput schema / properties / cluster / properties
      Added value: +{
+  "geography": {
+    "maxLength": 80,
+    "type": "string"
+  },
+  "primaryIntent": {
+    "enum": [
+      "informational",
+      "commercial",
+      "transactional",
+      "navigational"
+    ],
+    "type": "string"
+  },
+  "topic": {
+    "maxLength": 200,
+    "minLength": 3,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / cluster / required
      Added value: +[
+  "topic",
+  "primaryIntent"
+]
    • addedInput schema / properties / maxArticlesPerMonth / maximum
      Added value: +80
    • addedInput schema / properties / maxArticlesPerMonth / minimum
      Added value: +5
    • changedInput schema / properties / maxArticlesPerMonth / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / months / maximum
      Added value: +12
    • addedInput schema / properties / months / minimum
      Added value: +3
    • changedInput schema / properties / months / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / required
      Added value: +[
+  "brand",
+  "cluster",
+  "months",
+  "maxArticlesPerMonth"
+]
  2. First observed

TDQS

C2.1/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, so the description only needs to add extra behavioral context. It adds 'Inputs are validated server-side' and 'Returns a structured, audited deliverable,' which are useful but limited. No contradiction with annotations; the description does not disclose how errors or async behavior are handled.

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 relatively short, but it includes non-essential content such as 'Gapup agent-payable C-suite expertise (CMO)' and a reference case 'Notion — content engine 2026 (productivity B2B)' that do not aid tool selection or invocation. The useful part is limited to 'Returns a structured, audited deliverable' and the server-side validation note.

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?

For a tool with 5 parameters, nested objects, and no output schema, this description is grossly incomplete. It does not explain what the deliverable contains, how inputs determine the output, or how to use the async parameter. The agent is left with insufficient information to correctly invoke this 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% (only 'async' has a description). The tool description does not explain any of the parameters (brand, cluster, months, maxArticlesPerMonth) or their semantics. 'Send the documented case fields' defers to external documentation rather than providing meaning. This is a severe gap for a 5-parameter tool with nested objects.

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

Purpose2/5

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

The description is vague and lacks a specific verb+resource. 'Moteur de contenu' merely restates the tool name, and 'Returns a structured, audited deliverable' is generic. It does not explain what the content engine actually does (e.g., generate a content strategy, plan, or audit) and does not distinguish it from sibling content tools like content_audience_profile or content_ranking.

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 mentions a reference case (Notion) but does not specify conditions or contexts that favor this tool over others. The only usage hint is 'send the documented case fields,' which is not a decision guideline.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources