Skip to main content
Glama
revenue-enablement-mcp

revenue-enablement-mcp

Account Plan Builder

account_plan_builder
Read-only

Create a 90-day strategic account growth plan from account name, contacts, products, threats, and notes, with a power map, whitespace analysis, objection answers, and next steps.

Instructions

Helps you decide how to grow an account in the next 90 days. You give the account name, plus contacts, products, threats and notes if you have them. You get a strategic account plan: a power map with one row per contact you name, whitespace analysis, competitive questions, an answer for each objection and a 90 day plan. It does not look the account up. 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 deal_strategy_coach when you need an account-wide 90-day growth plan spanning contacts and products.

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": {
      "account_name": "<account_name>"
    },
    "name": "account_plan_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryNoIndustry vertical. Format is text. For example, "manufacturing".
current_arrNoCurrent ARR with this account (0 for prospects). Format is a JSON number. For example, 12.
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".
account_nameYesCompany/account name. Format is text. For example, "an approved anonymous manufacturer".
account_notesNoAny additional context about the account. Format is text. For example, "quarterly review completed with the finance lead".
your_solutionNoYour product/service offering. Format is text. For example, "invoice review service".
known_contactsNoKnown contacts and their roles, one per line or separated by semicolons, for example: Head of RevOps (champion); CFO. Each entry becomes one row, so put other notes in account notes. Format is text.
current_productsNoProducts/services they currently use from you. Format is text. For example, "manual invoice review".
competitive_threatsNoKnown competitors in the account. Format is text. For example, "renewal decision depends on a documented approval process".
expansion_opportunitiesNoPotential expansion areas or whitespace. Format is text. For example, "extend the pilot to a second finance team".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.2.33
    • changedInput schema / properties / account_name / description
      Previous value: -"Company/account name"New value: +"Company/account name. Format is text. For example, \"an approved anonymous manufacturer\"."
    • changedInput schema / properties / account_notes / description
      Previous value: -"Any additional context about the account"New value: +"Any additional context about the account. Format is text. For example, \"quarterly review completed with the finance lead\"."
    • changedInput schema / properties / competitive_threats / description
      Previous value: -"Known competitors in the account"New value: +"Known competitors in the account. Format is text. For example, \"renewal decision depends on a documented approval process\"."
    • changedInput schema / properties / current_arr / description
      Previous value: -"Current ARR with this account (0 for prospects)"New value: +"Current ARR with this account (0 for prospects). Format is a JSON number. For example, 12."
    • addedInput schema / properties / current_arr / minimum
      Added value: +0
    • changedInput schema / properties / current_products / description
      Previous value: -"Products/services they currently use from you"New value: +"Products/services they currently use from you. Format is text. For example, \"manual invoice review\"."
    • changedInput schema / properties / expansion_opportunities / description
      Previous value: -"Potential expansion areas or whitespace"New value: +"Potential expansion areas or whitespace. Format is text. For example, \"extend the pilot to a second finance team\"."
    • changedInput schema / properties / industry / description
      Previous value: -"Industry vertical"New value: +"Industry vertical. Format is text. For example, \"manufacturing\"."
    • changedInput schema / properties / known_contacts / description
      Previous value: -"Known contacts and their roles (can be rough notes)"New value: +"Known contacts and their roles, one per line or separated by semicolons, for example: Head of RevOps (champion); CFO. Each entry becomes one row, so put other notes in account notes. Format is text."
    • 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/service offering"New value: +"Your product/service offering. Format is text. For example, \"invoice review service\"."
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: no account lookup, no sign-in, no storage of inputs or outputs, hosted usage metadata recorded, and error behavior that names the field to supply or fix. These disclosures cover privacy, authentication, and failure modes that readOnlyHint/openWorldHint alone could not convey.

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 and deliverables, then constraints, then the alternative — a logical order with no filler sentences. The output enumeration is somewhat listy and could be trimmed, but each sentence carries distinct information.

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 no output schema, the description compensates by describing what the response contains (power map, whitespace analysis, competitive questions, objection answers, 90-day plan). Combined with the error behavior and data-handling statements, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all 10 parameters including the enum and formats; a 3 baseline applies. The description groups the optional inputs ('contacts, products, threats and notes') and explains that each named contact becomes one row, but adds no format or syntax detail beyond the schema.

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?

States a specific outcome ('strategic account plan' for growth 'in the next 90 days') and enumerates the concrete deliverables: power map with one row per contact, whitespace analysis, competitive questions, objection answers, and a 90-day plan. It also clearly distinguishes itself from deal_strategy_coach by scope (account-wide, spanning contacts and products).

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

Usage Guidelines5/5

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

Gives explicit routing guidance: 'Use this instead of deal_strategy_coach when you need an account-wide 90-day growth plan spanning contacts and products.' It also states what inputs are required vs. optional ('account name, plus contacts, products, threats and notes if you have them') and clarifies a boundary condition ('It does not look the account up').

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