Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

outbound_sequencer

Read-only

Séquences outbound — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub → CFO + CRO B2B SaaS France — Séquence 6 touches multi-canal · Taux réponse +180%. Inputs are validated server-side — send the documented case fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icpYes
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.
offerYes
excludedAnglesNo
targetAccountsNo

Schema Changelog

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

  1. Changed9 schema fields changed
    • addedInput schema / properties / excludedAngles / maxLength
      Added value: +400
    • addedInput schema / properties / icp / properties
      Added value: +{
+  "companySize": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  },
+  "geography": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  },
+  "personas": {
+    "items": {
+      "enum": [
+        "ceo",
+        "cfo",
+        "cmo",
+        "cto",
+        "vp-sales",
+        "vp-ops",
+        "chro",
+        "founder",
+        "procurement",
+        "other"
+      ],
+      "type": "string"
+    },
+    "maxItems": 4,
+    "minItems": 1,
+    "type": "array"
+  },
+  "sector": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / icp / required
      Added value: +[
+  "sector",
+  "companySize",
+  "geography",
+  "personas"
+]
    • addedInput schema / properties / offer / properties
      Added value: +{
+  "mainBenefit": {
+    "maxLength": 200,
+    "minLength": 10,
+    "type": "string"
+  },
+  "name": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "valueProposition": {
+    "maxLength": 400,
+    "minLength": 20,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / offer / required
      Added value: +[
+  "name",
+  "valueProposition",
+  "mainBenefit"
+]
    • addedInput schema / properties / targetAccounts / items
      Added value: +{
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / targetAccounts / maxItems
      Added value: +5
    • addedInput schema / properties / targetAccounts / minItems
      Added value: +1
    • addedInput schema / required
      Added value: +[
+  "offer",
+  "icp"
+]
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's mention of 'returns a structured, audited deliverable' is consistent and adds minor context. No destructive behavior is implied, and inputs validated server-side is noted. Adequate but not rich.

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?

Four sentences, but includes a specific reference case that may not be necessary for general use. Could be more concise by removing the example or stating a generic purpose first.

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 (5 parameters with nested objects, no output schema), the description is incomplete. It lacks details on the output format, how to interpret results, or any prerequisites. The sibling list is large, so more context is needed.

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% (only 'async' has a description). The description does not explain parameters like 'offer' or 'icp' beyond the schema. The reference case hints at structure but does not compensate for the low coverage.

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 mentions 'Séquences outbound' and 'agent-payable C-suite expertise (CRO)' and says it returns a structured deliverable, but relies heavily on a specific reference case (Gapup Hub) without a clear general statement. The purpose is somewhat clear but not fully distilled for general understanding.

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 among the many sibling tools. The description does not mention prerequisites, scenarios, 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