Andru

Plan your first sales hire

get_sales_blueprint

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companyStage": "<companyStage>",
      "arrTarget": "<arrTarget>"
    },
    "name": "get_sales_blueprint"
  }
}

Input Schema

Name	Required	Description
`quoteId`	No	Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes).
`dealSize`	No	Average deal size (e.g., "$15K ACV", "$50K ACV"). Infer from context or ask.
`teamSize`	No	Current team size. Infer from context if mentioned.
`arrTarget`	Yes	Annual recurring revenue target (e.g., "$2M", "$5M", "$10M"). Ask the user if not mentioned.
`companyStage`	Yes	Current funding stage. Infer from conversation context if the user has mentioned it.
`avgCycleLength`	No	Average sales cycle length (e.g., "30 days", "60 days", "90+ days"). Infer or ask.
`idempotencyKey`	No	Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.
`maxAmountCents`	No	Optional: 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.

Changed1 schema field changedOct 23, 2026

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"
+}

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already flag this as a non-read-only, open-world generation call with no destructive effect; the description adds the useful fact that it produces a concrete multi-part deliverable. It says nothing about the paid nature (quoteId, maxAmountCents, idempotencyKey imply a charge), latency, or whether output can be regenerated, which are the traits that matter for a paid generation tool.

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?

Two dense sentences, with the triggering condition front-loaded before the deliverable list. Slightly overstuffed in the second half but every clause maps to a real output; no filler.

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 return contents, and annotations cover the safety profile — enough for an agent to call it correctly. The gap is the commercial behavior (that this consumes a quote and can be charged), which is left entirely 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 all eight parameters are documented structurally; the description merely nods to the ARR goal link. Baseline 3 is appropriate — no syntax, inference rules, or parameter trade-offs are added 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, recognizable trigger (founder handing a proven path to a first seller) and enumerates the exact resource produced: role definition, comp, interview loop, and ramp. An agent can distinguish this from all siblings, none of which cover hiring planning.

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 when-to-use is explicit and narrow — planning a first sales hire, choosing the role, setting pay, interviewing, or ramping. It lacks any explicit when-not or named alternative, but no sibling overlaps, so the routing signal is clear.

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

All Andru tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.