Skip to main content
Glama

get_sales_blueprint

Read-only

Generate a comprehensive sales hiring blueprint including job descriptions, compensation structures, interview questions, ramp plans, and activity targets aligned with revenue goals.

Instructions

Builds everything you need to make your first sales hire — job description, comp structure, interview questions that actually reveal sales ability, 90-day ramp plan, and weekly activity targets tied to your ARR goal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyStageYesCurrent funding stage. Infer from conversation context if the user has mentioned it.
arrTargetYesAnnual recurring revenue target (e.g., "$2M", "$5M", "$10M"). Ask the user if not mentioned.
dealSizeNoAverage deal size (e.g., "$15K ACV", "$50K ACV"). Infer from context or ask.
avgCycleLengthNoAverage sales cycle length (e.g., "30 days", "60 days", "90+ days"). Infer or ask.
teamSizeNoCurrent team size. Infer from context if mentioned.

Implementation Reference

  • src/catalog.js:405-435 (registration)
    The tool 'get_sales_blueprint' is defined and registered in the static tool catalog. It proxies to the backend, so the 'execution' logic is not implemented locally in this codebase.
      name: 'get_sales_blueprint',
      description: 'Builds everything you need to make your first sales hire — job description, comp structure, interview questions that actually reveal sales ability, 90-day ramp plan, and weekly activity targets tied to your ARR goal.',
      annotations: READ_ONLY,
      inputSchema: {
        type: 'object',
        properties: {
          companyStage: {
            type: 'string',
            enum: ['Pre-Seed', 'Seed', 'Series A', 'Series B'],
            description: 'Current funding stage. Infer from conversation context if the user has mentioned it.',
          },
          arrTarget: {
            type: 'string',
            description: 'Annual recurring revenue target (e.g., "$2M", "$5M", "$10M"). Ask the user if not mentioned.',
          },
          dealSize: {
            type: 'string',
            description: 'Average deal size (e.g., "$15K ACV", "$50K ACV"). Infer from context or ask.',
          },
          avgCycleLength: {
            type: 'string',
            description: 'Average sales cycle length (e.g., "30 days", "60 days", "90+ days"). Infer or ask.',
          },
          teamSize: {
            type: 'number',
            description: 'Current team size. Infer from context if mentioned.',
          },
        },
        required: ['companyStage', 'arrTarget'],
      },
    },
Behavior4/5

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

Annotations indicate read-only and open-world hints, but the description adds valuable behavioral context: it's a comprehensive generator tool that creates multiple artifacts (not just a single document). The description doesn't contradict annotations and provides insight into the scope and output nature beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that efficiently communicates the tool's comprehensive output. Every word contributes to understanding the tool's purpose without redundancy or unnecessary elaboration.

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

Completeness4/5

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

For a generative tool with read-only/open-world annotations but no output schema, the description adequately conveys what will be produced. However, it doesn't specify format (e.g., document type, structure) or whether outputs are editable/templates, leaving some implementation details unclear.

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?

With 100% schema description coverage, the schema already documents all 5 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions, so it meets the baseline expectation without providing extra semantic value.

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 clearly states the specific action ('Builds everything you need') and the comprehensive output (job description, comp structure, interview questions, ramp plan, activity targets). It distinguishes itself from siblings by focusing on sales hiring infrastructure rather than prospecting, classification, or other sales-related functions.

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

Usage Guidelines3/5

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

The description implies usage context ('to make your first sales hire') but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided about prerequisites, timing, or comparison to other tools like 'get_icp_profile' or 'simulate_buyer_persona' that might be related to sales planning.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/geter-andru/andru-revenue-intelligence'

If you have feedback or need assistance with the MCP directory API, please join our Discord server