Andru

Build an account plan

get_account_plan

Use this when the person wants a plan for a specific target account. Builds a first map of the buying committee, the opportunities that fit what they sell, the likely champion, what each person needs to hear, and next steps, from sourced research, saved to their Andru account. Treat the committee and champion as a map to confirm with each person. Returns the plan's link with a short summary. A plan for the same company from the last 30 days comes back at once. Takes 1 to 3 minutes: returns a job_id; call get_asset with it.

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": {
      "accountName": "<accountName>"
    },
    "name": "get_account_plan"
  }
}

Input Schema

Name	Required	Description
`quoteId`	No	Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes).
`refresh`	No	Build a new plan even if one from the last 30 days exists. Default false.
`accountName`	Yes	The company to plan for.
`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.
`productDescription`	No	What you sell to this account, if different from the product saved in Andru (a sentence or two).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / refresh / description

Previous value: -"Build a new plan even if one from the last 30 days exists ($12). Default false."New value: +"Build a new plan even if one from the last 30 days exists. Default false."

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / accountName / description

Previous value: -"The company to plan for, e.g. \"Acme Logistics\"."New value: +"The company to plan for."

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

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses asynchronous execution (1-3 minutes), the returned job_id and the get_asset follow-up, the 30-day result cache, that the output is persisted to the Andru account, and cost mechanics (quoted price held 30 minutes, maxAmountCents guard, no double charge). It also flags a reliability caveat — the committee/champion is a map to confirm, not ground truth.

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?

Front-loads the trigger, then deliverables, then the confidence caveat, then return shape and latency. No sentence is redundant — even the caveat about confirming the committee earns its place as a usage warning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the return-value burden and does so ('returns the plan's link with a short summary', or a job_id). Latency, cost, caching and the follow-up call are all covered, leaving nothing an agent needs before invoking it.

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 the baseline is 3; the description nonetheless adds real meaning by explaining the caching behavior that makes `refresh` matter and by framing the async job_id contract. It leaves quoteId, idempotencyKey and maxAmountCents to the schema, which describes them adequately.

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 and resource ('Builds a first map of the buying committee...') and a concrete trigger condition ('when the person wants a plan for a specific target account'). The enumerated deliverables (committee map, fit opportunities, champion, per-person messaging, next steps) make it unmistakable against siblings like get_pre_brief or generate_asset.

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 and explains the cached-result path ('a plan for the same company from the last 30 days comes back at once') plus the refresh override for the alternative. It does not name or exclude any sibling tool, so an agent must infer when get_pre_brief or generate_asset would be preferable.

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.