Skip to main content
Glama
closermethod

SMB Sales Intelligence MCP

get_pricing_framework

Get a 3-option pricing framework and templates to present pricing options to small business customers.

Instructions

Get the 3-option pricing framework and templates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/main.ts:723-731 (registration)
    Tool 'get_pricing_framework' is registered in the ListToolsRequestSchema handler with name, description, and empty inputSchema.
    {
      name: "get_pricing_framework",
      description: "Get the 3-option pricing framework and templates.",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Handler case for 'get_pricing_framework' in CallToolRequestSchema — returns the PRICING_FRAMEWORK data as JSON.
    case "get_pricing_framework": {
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            module: "3-Option Pricing Framework",
            ...PRICING_FRAMEWORK
          }, null, 2)
        }]
      };
    }
  • PRICING_FRAMEWORK constant definition containing the 3-option pricing psychology, structure, template, rules, and discount handling.
    const PRICING_FRAMEWORK = {
      psychology: "One price = 'Is this worth it?' Three options = 'Which one do I want?'",
      structure: {
        option_a: {
          role: "Starter - Easy entry, low risk",
          pricing: "Your base rate",
          purpose: "For price-sensitive buyers or those who need a 'test'"
        },
        option_b: {
          role: "Most Popular - What you WANT them to pick",
          pricing: "1.7-2x Option A",
          purpose: "Best value for them, best margin for you"
        },
        option_c: {
          role: "Premium - Anchors the others",
          pricing: "2.5-3x Option A",
          purpose: "Makes B look reasonable. Some will actually pick C."
        }
      },
      template: `Based on what you shared, here are 3 options:
    
    **Option A (Starter):** [Deliverable] — $[price]
    • [Scope details]
    • [What's included]
    • Best for: [who this is for]
    
    **Option B (Most Popular ⭐):** [Deliverable] — $[price]
    • [Scope details]
    • [What's included]
    • Best for: [who this is for]
    
    **Option C (Premium):** [Deliverable] — $[price]
    • [Scope details]
    • [What's included]
    • Best for: [who this is for]
    
    Happy to walk through any of these. Which feels closest to what you need?`,
      rules: [
        "ALWAYS present 3 options — never just 1",
        "Label Option B as 'Most Popular' or put a star next to it",
        "If they ask for discount, reduce scope (offer A) — never reduce B's price",
        "If they want something between A and B, create a new B with adjusted scope",
        "Option C should feel luxurious, not ridiculous"
      ],
      handling_discount_requests: {
        request: "Can you do any better on price?",
        response: "I hear you. Here's what I can do: I can adjust the scope to fit a smaller budget. Would Option A work, or do you need something specific from Option B?",
        rule: "Trade scope for price — never just lower the number."
      }
    };
Behavior2/5

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

No annotations are provided, and the description only states it 'gets' data, implying a read-only operation. It does not disclose any behavioral traits such as authentication requirements, potential errors, or what happens if the framework is unavailable.

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, clear sentence with no superfluous words. It is appropriately sized for the tool's simplicity.

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

Completeness3/5

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

Given the low complexity (no parameters, no output schema), the description is minimally adequate—it explains what the tool retrieves. However, it could be more helpful by mentioning the format or structure of the returned data (e.g., types of templates).

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?

There are no parameters in the input schema, so the description does not need to explain parameter behavior. The baseline for zero parameters is 4, and the description adds no additional parameter information, which is acceptable.

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 states the verb 'Get' and clearly specifies 'pricing framework and templates' with '3-option' detail. While it distinguishes from sibling tools by focusing on pricing, it does not explicitly differentiate from similar content retrieval tools like get_full_playbook.

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 context is provided on when to use this tool versus alternatives among the many 'get_*' siblings. There is no guidance on prerequisites, typical use cases, or when not to use it.

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/closermethod/smb-sales-intelligence-mcp'

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