Skip to main content
Glama
revenue-enablement-mcp

revenue-enablement-mcp

Demo Script Builder

demo_script_builder
Read-only

Builds a timed demo script from the demo type, persona, use case, must-show features, and named pains, mapping each step to pains with spoken lines, discussion, close, and follow-up.

Instructions

Helps you decide what to show in a demo, and in what order. You give the demo type, the persona and the use case, plus the features you must show and the pains you name. You get a timed run from opening to close, with spoken lines and a step for each feature tied to the pains, then discussion, close and follow up lines and sector notes. The answer says where each step came from and what it did not get. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of sales_enablement_content when you need a timed product demonstration tied to the use case.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "demo_type": "<demo_type>",
      "your_solution": "<your_solution>"
    },
    "name": "demo_script_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
attendeesNoOther attendees and their roles. Format is text. For example, "procurement lead and security reviewer".
demo_typeYesType of demo. Format is text using one of the listed labels. For example, "first_look".
your_sectorNoOptional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech".
demo_durationNoDemo duration in minutes. Format is a JSON number. For example, 12.
your_solutionYesYour product/solution. Format is text. For example, "invoice review service".
desired_outcomeNoWhat you want to achieve from this demo. Format is text. For example, "resolve invoice exceptions before month-end".
key_pain_pointsNoPain points to address in demo. Format is text. For example, "invoice exceptions delay month-end close".
known_objectionsNoKnown objections to address. Format is text. For example, "The reviewer asked who owns unresolved exceptions.".
primary_audienceNoPrimary demo audience (role/persona). Format is text. For example, "finance leaders at manufacturers".
customer_industryNoCustomer industry. Format is text. For example, "manufacturing".
competitor_contextNoCompetitor being displaced or compared. Format is text. For example, "renewal decision depends on a documented approval process".
must_show_featuresNoFeatures that must be demonstrated. Format is text. For example, "exception queue and approval history".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.2.33
    • changedInput schema / properties / attendees / description
      Previous value: -"Other attendees and their roles"New value: +"Other attendees and their roles. Format is text. For example, \"procurement lead and security reviewer\"."
    • changedInput schema / properties / competitor_context / description
      Previous value: -"Competitor being displaced or compared"New value: +"Competitor being displaced or compared. Format is text. For example, \"renewal decision depends on a documented approval process\"."
    • changedInput schema / properties / customer_industry / description
      Previous value: -"Customer industry"New value: +"Customer industry. Format is text. For example, \"manufacturing\"."
    • changedInput schema / properties / demo_duration / description
      Previous value: -"Demo duration in minutes"New value: +"Demo duration in minutes. Format is a JSON number. For example, 12."
    • addedInput schema / properties / demo_duration / minimum
      Added value: +0
    • changedInput schema / properties / demo_type / description
      Previous value: -"Type of demo"New value: +"Type of demo. Format is text using one of the listed labels. For example, \"first_look\"."
    • changedInput schema / properties / desired_outcome / description
      Previous value: -"What you want to achieve from this demo"New value: +"What you want to achieve from this demo. Format is text. For example, \"resolve invoice exceptions before month-end\"."
    • changedInput schema / properties / key_pain_points / description
      Previous value: -"Pain points to address in demo"New value: +"Pain points to address in demo. Format is text. For example, \"invoice exceptions delay month-end close\"."
    • changedInput schema / properties / known_objections / description
      Previous value: -"Known objections to address"New value: +"Known objections to address. Format is text. For example, \"The reviewer asked who owns unresolved exceptions.\"."
    • changedInput schema / properties / must_show_features / description
      Previous value: -"Features that must be demonstrated"New value: +"Features that must be demonstrated. Format is text. For example, \"exception queue and approval history\"."
    • changedInput schema / properties / primary_audience / description
      Previous value: -"Primary demo audience (role/persona)"New value: +"Primary demo audience (role/persona). Format is text. For example, \"finance leaders at manufacturers\"."
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, \"logistics_tech\".",
      +  "enum": [
      +    "logistics_tech",
      +    "fintech",
      +    "saas",
      +    "vertical_saas",
      +    "ai_native",
      +    "ites",
      +    "telecom",
      +    "software",
      +    "cybersecurity",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / your_solution / description
      Previous value: -"Your product/solution"New value: +"Your product/solution. Format is text. For example, \"invoice review service\"."
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=true, openWorldHint=false, destructiveHint=false), the description discloses that no sign-in is needed, no inputs or outputs are stored, hosted usage metadata is recorded, and that missing required fields or invalid values return a named error. That is meaningful context an agent cannot get from the annotation block alone, though it stops short of describing latency, rate limits or response shape.

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?

Front-loaded with purpose first, then inputs, then outputs, then operational caveats and the sibling routing rule. It is on the long side and the input/output framing repeats "You give/You get", but every sentence carries distinct information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 parameters, no output schema, and a complex generative result, the description carries the full burden and does so: it explains what the response contains (timed script, per-feature steps, sector notes), how provenance is reported ("where each step came from and what it did not get"), and what error behavior to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns a bump by explaining how inputs drive outputs, notably that your_sector determines the sector notes and falls back to inference from the user's words. It also names the key input families (demo type, persona, use case, must-show features, pains) that an agent should prioritize filling.

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 states a specific verb and resource ("decide what to show in a demo, and in what order") and enumerates the concrete artifact produced: a timed run from opening to close with spoken lines, steps tied to pains, discussion, close, follow-up and sector notes. It also names a sibling it replaces, so an agent can separate it from the other builder tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives an explicit selection rule at the end: use this instead of sales_enablement_content when a timed product demonstration tied to the use case is needed. That is real routing guidance, but it names only one alternative and offers no when-not-to-use condition or prerequisites beyond the required input fields.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.