Skip to main content
Glama

get_messaging_framework

Read-only

Generate tailored messaging frameworks for enterprise sales by adapting content to buyer personas, communication channels, and funnel stages using MBTI-based customization.

Instructions

Get the exact words to use — for a specific buyer type, channel, and funnel stage. MBTI-adapted so the analytical CTO and the results-driven VP Sales get different versions. Returns value props, objection responses, voice variants, and outbound templates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
segmentNoTarget segment or vertical
stageNoWhere the buyer is in their journey
channelNoChannel (email, linkedin, phone, etc.)
personaTypeNoTarget buyer title
mbtiCategoryNoMBTI communication category for message adaptation
productDescriptionNoA brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: "What does your product do, and who do you sell to?" before calling this tool.
verticalNoThe industry the user sells into (e.g., "fintech", "healthcare", "defense"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask.
targetRoleNoThe buyer role being evaluated (e.g., "CFO", "CTO", "VP Sales"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical.

Implementation Reference

  • The server delegates tool execution to the Andru API client via `client.callTool(name, args)`.
    const { name, arguments: args } = request.params;
    try {
      return await client.callTool(name, args || {});
  • The tool 'get_messaging_framework' is defined in the static catalog, specifying its purpose and input parameters.
    name: 'get_messaging_framework',
    description: 'Get the exact words to use — for a specific buyer type, channel, and funnel stage. MBTI-adapted so the analytical CTO and the results-driven VP Sales get different versions. Returns value props, objection responses, voice variants, and outbound templates.',
    annotations: READ_ONLY,
    inputSchema: {
      type: 'object',
      properties: {
        segment: { type: 'string', description: 'Target segment or vertical' },
        stage: {
          type: 'string',
          enum: ['awareness', 'consideration', 'decision'],
          description: 'Where the buyer is in their journey',
        },
        channel: { type: 'string', description: 'Channel (email, linkedin, phone, etc.)' },
        personaType: { type: 'string', description: 'Target buyer title' },
        mbtiCategory: {
Behavior3/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation with open-world data. The description adds value by specifying that it returns multiple messaging components (value props, objection responses, etc.) and adapts to MBTI categories, which provides useful behavioral context beyond the annotations. However, it does not disclose details like rate limits, authentication needs, or potential data freshness issues.

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 highly concise and front-loaded, consisting of two sentences that efficiently convey the tool's purpose and output. Every word earns its place, with no redundant information or fluff, making it easy for an AI agent to quickly understand the tool's function.

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?

Given the tool's complexity (8 parameters, no output schema) and rich annotations, the description is mostly complete. It clearly states what the tool does and returns, but it could improve by hinting at the output structure or format, especially since there is no output schema. However, it adequately covers the core functionality for a read-only tool with open-world data.

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 description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description adds minimal semantic value beyond the schema by implying that parameters like 'mbtiCategory' and 'stage' drive message adaptation, but it does not elaborate on how they interact or provide examples. This meets the baseline score of 3 for high schema coverage.

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 tool's purpose with specific verbs ('Get the exact words to use') and resources (value props, objection responses, voice variants, outbound templates). It distinguishes itself from siblings by focusing on MBTI-adapted messaging for specific buyer types, channels, and funnel stages, which is unique among the listed tools that cover broader sales, prospecting, and analysis functions.

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?

The description provides clear context for when to use this tool: for generating tailored messaging based on buyer type (MBTI-adapted), channel, and funnel stage. However, it does not explicitly state when not to use it or name specific alternatives among the sibling tools, such as 'get_persona_profile' or 'simulate_buyer_persona', which might overlap in persona-related contexts.

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