Skip to main content
Glama
Sign In
Andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Plan your first sales hire

get_sales_blueprint

Create a comprehensive hiring blueprint for new sales talent. Define job roles, comp structures, interview questions, and 90-day ramp plans tailored to your ARR goals.

Instructions

When the founder is ready to hand the path they've proven to a first seller: use this when the person is planning a sales hire: what role, how to pay it, how to interview for it, or how to ramp the new hire. Returns a job description, comp structure, interview questions that reveal sales ability, a 90-day ramp plan and weekly activity targets tied to their ARR goal. Paid. Check the price with quote before running.

Input Schema

NameRequiredDescriptionDefault
quoteIdNoOptional: the quote_id from quote, to pay the quoted price (held for 30 minutes).
dealSizeNoAverage deal size (e.g., "$15K ACV", "$50K ACV"). Infer from context or ask.
teamSizeNoCurrent team size. Infer from context if mentioned.
arrTargetYesAnnual recurring revenue target (e.g., "$2M", "$5M", "$10M"). Ask the user if not mentioned.
companyStageYesCurrent funding stage. Infer from conversation context if the user has mentioned it.
avgCycleLengthNoAverage sales cycle length (e.g., "30 days", "60 days", "90+ days"). Infer or ask.
idempotencyKeyNoOptional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.
maxAmountCentsNoOptional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.9
    • addedInput schema / properties / idempotencyKey
      Added value: +{
+  "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.",
+  "type": "string"
+}
    • addedInput schema / properties / maxAmountCents
      Added value: +{
+  "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / quoteId
      Added value: +{
+  "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes).",
+  "type": "string"
+}
  2. First observedv1.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds real value beyond annotations: discloses that the call is paid and that the price must be checked via quote first — critical for a non-read-only, open-world tool. It doesn't cover timeout/expiry of the quote or what happens on failure, but the cost-gating workflow is the key disclosure.

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?

Front-loads the trigger condition, then the deliverables, then the payment prerequisite. Slightly dense and the opening clause ('hand the path they've proven to a first seller') is a bit ornate, but no sentence is wasted.

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 no output schema, the description usefully enumerates what comes back, and it covers the paid prerequisite. An agent has enough to invoke it correctly; only edge cases (quote expiry, failure semantics) are left to the schema.

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, including inference hints and the idempotency/maxAmountCents safeguards. The description only implicitly links arrTarget to the activity targets and adds no parameter-level detail beyond the schema.

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?

States a specific verb+resource and enumerates the concrete deliverables (job description, comp structure, interview questions, 90-day ramp plan, activity targets tied to ARR goal), which makes it unmistakably distinct from siblings like generate_asset or get_account_plan.

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?

Gives a clear triggering condition ('when the person is planning a sales hire') plus the sub-questions it answers (what role, how to pay, how to interview, how to ramp). No explicit exclusions or named alternatives are stated, but the use case is unambiguous.

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