Skip to main content
Glama
geter-andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_messaging_framework

Read-only

Generate buyer-specific messaging frameworks for B2B outreach: tailor value propositions, objection answers, voice variants, and templates by role, channel, funnel stage, and communication style.

Instructions

Words that fit each buyer, by buyer type, channel and funnel stage, adapted to how each person prefers to communicate, so the analytical CTO and the results-driven VP Sales each get a version that fits them. Returns value propositions, answers to the concerns each buyer raises, voice variants and outbound templates. Set mbtiCategory for one communication style, or leave it out to get all four. Use get_persona_profile to learn who the buyer is, and get_pre_brief to prepare for one specific meeting. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stageNoWhere the buyer is in their journey
channelNoChannel (email, linkedin, phone, etc.)
segmentNoTarget segment or vertical
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.
personaTypeNoTarget buyer title
mbtiCategoryNoCommunication style to adapt the message to
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.1
    • changedInput schema / properties / mbtiCategory / description
      Previous value: -"MBTI communication category for message adaptation"New value: +"Communication style to adapt the message to"
  2. First observedv1.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description usefully adds that the tool is free and enumerates the returned content categories, which matters because no output schema exists. It still doesn't disclose generation latency or determinism, but the added cost and return context is solid beyond the annotations.

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?

It is front-loaded with purpose, then returns, then parameter guidance, then routing, then 'Free.' Every sentence earns its place. The opening sentence is slightly overwrought but not wasteful.

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?

With 8 parameters, no output schema and a read-only annotation profile, the description covers what the tool produces and when to reach for it, including cost. It is complete enough to invoke correctly, though it omits any note on output size or limits across the four MBTI variants.

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 coverage is 100%, so baseline is 3, but the description adds genuine meaning: set mbtiCategory for a single communication style or omit it to get all four, which is not derivable from the enum alone. Inference guidance for vertical/targetRole is echoed in the schema, so no extra credit there.

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 resource (messaging framework) and scope precisely: words adapted by buyer type, channel, funnel stage and communication style. It then enumerates the concrete outputs (value propositions, objection answers, voice variants, outbound templates). The first sentence is flowery, but the second grounds it well enough for an agent to distinguish it from siblings.

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 explicitly routes to two alternatives with conditions: use get_persona_profile to learn who the buyer is, and get_pre_brief for one specific meeting. It also explains the optional mbtiCategory behavior (one style vs all four). It does not distinguish from generate_asset, a potential overlap, so not a full 5.

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

Deploy Server

Other Tools