Skip to main content
Glama
geter-andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

simulate_buyer_persona

Role-play with buyer personas like CFO, CTO, or VP Sales to practice sales conversations turn by turn, then get a scored debrief before the real meeting.

Instructions

Prepare for a key meeting with the buying committee. Andru acts as key decision-makers asking you questions your real buyers ask so you come into real-world meetings equipped to succeed. A Deal Prep session is $5 for 25 turns: open it, reply turn by turn with the session_id, and say "End role-play. How did I do?" for a scored debrief.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoopening = open a session ($5) and get the buyer's opening line. reply = send the seller's next message on session_id. list = available personas. Default: opening.
messageNomode=reply: what the seller says to the buyer. "End role-play. How did I do?" ends with a debrief.
personaNoWhich buyer to simulate. Pick based on who the user is preparing to meet.
stageIdNoBuyer journey stage (1=Researching through 7=Advocating). Default: 3.
session_idNoThe Deal Prep session to continue (returned by mode=opening). Required for mode=reply.
productNameNoProduct name. Infer from context.
session_keyNoOptional idempotency key for opening a session: retrying with the same key never charges twice.
productDescriptionNoWhat the user's product does. Infer from conversation context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.4.1
    • addedInput schema / properties / message
      Added value: +{
+  "description": "mode=reply: what the seller says to the buyer. \"End role-play. How did I do?\" ends with a debrief.",
+  "type": "string"
+}
    • changedInput schema / properties / mode / description
      Previous value: -"opening = buyer's opening message. list = available personas. Default: opening."New value: +"opening = open a session ($5) and get the buyer's opening line. reply = send the seller's next message on session_id. list = available personas. Default: opening."
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "opening",
-  "list"
-]New value: +[
+  "opening",
+  "reply",
+  "list"
+]
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "The Deal Prep session to continue (returned by mode=opening). Required for mode=reply.",
+  "type": "string"
+}
    • addedInput schema / properties / session_key
      Added value: +{
+  "description": "Optional idempotency key for opening a session: retrying with the same key never charges twice.",
+  "type": "string"
+}
    • changedInput schema / properties / stageId / description
      Previous value: -"Buyer journey stage (0=Unaware through 7=Advocating). Default: 3."New value: +"Buyer journey stage (1=Researching through 7=Advocating). Default: 3."
    • changedInput schema / properties / stageId / enum
      Previous value: -[
-  0,
-  1,
-  2,
-  3,
-  4,
-  5,
-  6,
-  7
-]New value: +[
+  1,
+  2,
+  3,
+  4,
+  5,
+  6,
+  7
+]
    • changedInput schema / required
      Previous value: -[
-  "persona"
-]New value: +[]
  2. First observedv1.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare this is mutating and open-world, but the description adds genuinely non-derivable facts: the $5 charge, the 25-turn cap, the session lifecycle, and the scored-debrief ending. These are important behavioral traits an agent cannot infer from structured fields. It doesn't explain what happens on turn exhaustion or session expiry, keeping it from a 5.

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?

Three sentences, front-loaded with the purpose followed by mechanics and pricing. The 'Andru acts as...' sentence is slightly promotional but carries the role-play framing. No wasted sentences, though it could be tightened.

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 an 8-parameter, multi-mode tool with no output schema, the description covers the session workflow, cost, turn limit, and debrief path adequately. It leaves the exact return shape of each mode unstated, but the schema carries the mode semantics, so the definition is largely complete.

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%, so every parameter is already documented in the schema (mode, session_id, message, etc.). The description's 'reply turn by turn with the session_id' reinforces the reply flow but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 a specific verb and resource: it simulates a buyer persona ('Andru acts as key decision-makers') for deal preparation. The purpose is clear and distinct from pure data-retrieval siblings. It stops short of naming alternatives like get_persona_profile or get_pre_brief, so an agent gets no explicit sibling differentiation.

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?

Clear context is given: use it to 'Prepare for a key meeting with the buying committee,' with a concrete three-step workflow (open, reply turn by turn, end with the debrief phrase). There are no explicit exclusions or named alternatives, so it lands at clear-context-but-no-routing rather than 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