Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

proposal_generator

Read-only

Générateur de propositions commerciales — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Spendesk × Gapup Hub — Proposition 7 sections · ROI 3Y €1.8M · Payback 4 mois. 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.
offerYes
companyYes
prospectYes
dealContextNo

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: +{
+  "name": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector"
+]
    • addedInput schema / properties / dealContext / properties
      Added value: +{
+  "budget": {
+    "type": "string"
+  },
+  "competitors": {
+    "items": {
+      "maxLength": 100,
+      "type": "string"
+    },
+    "maxItems": 3,
+    "minItems": 0,
+    "type": "array"
+  },
+  "decisionTimeline": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / offer / properties
      Added value: +{
+  "mainBenefits": {
+    "items": {
+      "maxLength": 200,
+      "type": "string"
+    },
+    "maxItems": 6,
+    "minItems": 2,
+    "type": "array"
+  },
+  "pricing": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "productName": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "useCase": {
+    "maxLength": 300,
+    "minLength": 10,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / offer / required
      Added value: +[
+  "productName",
+  "pricing",
+  "mainBenefits",
+  "useCase"
+]
    • addedInput schema / properties / prospect / properties
      Added value: +{
+  "contactName": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  },
+  "contactTitle": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  },
+  "name": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / prospect / required
      Added value: +[
+  "name",
+  "sector",
+  "contactName",
+  "contactTitle"
+]
    • addedInput schema / required
      Added value: +[
+  "company",
+  "prospect",
+  "offer"
+]
  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 the deliverable is "audited," which provides some behavioral context beyond annotations, but it does not detail permissions, rate limits, or side effects.

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 (3 sentences) and front-loads the purpose. The inclusion of a reference case adds length but provides useful context; however, it could be more tightly written.

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 (5 parameters, nested objects, no output schema), the description is incomplete. It lacks details on output format, how to use the async parameter, and input formatting beyond "send the documented case fields." This forces the agent to rely on the schema, which has low coverage.

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%. The description does not explain the required fields (company, prospect, offer) or their structure. The phrase "documented case fields" is vague and does not compensate for the low coverage, leaving parameter meaning unclear.

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 the tool generates commercial proposals ("Générateur de propositions commerciales") and returns a structured deliverable. The reference case provides concrete context. However, it does not explicitly differentiate from sibling tools, which is a minor gap.

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 fails to provide any guidance on when to use or avoid this tool. It omits prerequisites, context, or alternatives, leaving the agent without decision-support information.

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