Skip to main content
Glama
Sign In
Andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Build an account plan

get_account_plan

Builds a sourced research plan for a target account, mapping the buying committee, best-fit opportunities, likely champion, and next steps, then saves it to your Andru account.

Instructions

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. 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).
refreshNoBuild a new plan even if one from the last 30 days exists ($12). Default false.
accountNameYesThe company to plan for.
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.
productDescriptionNoWhat 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.

  1. Changed1 schema field changedv1.4.10
    • changedInput schema / properties / accountName / description
      Previous value: -"The company to plan for, e.g. \"Acme Logistics\"."New value: +"The company to plan for."
  2. 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"
+}
  3. Changed7 schema fields changedv1.4.8
    • changedInput schema / properties / accountName / description
      Previous value: -"Target account/company name"New value: +"The company to plan for, e.g. \"Acme Logistics\"."
    • removedInput schema / properties / dealContext
      Removed value: -{
-  "description": "Current deal context",
-  "properties": {
-    "nextMeeting": {
-      "description": "Next meeting date/context",
-      "type": "string"
-    },
-    "stage": {
-      "description": "Current deal stage",
-      "type": "string"
-    },
-    "value": {
-      "description": "Deal value",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}
    • removedInput schema / properties / domain
      Removed value: -{
-  "description": "Company domain",
-  "type": "string"
-}
    • removedInput schema / properties / industry
      Removed value: -{
-  "description": "Industry vertical",
-  "type": "string"
-}
    • addedInput schema / properties / productDescription
      Added value: +{
+  "description": "What you sell to this account, if different from the product saved in Andru (a sentence or two).",
+  "type": "string"
+}
    • addedInput schema / properties / refresh
      Added value: +{
+  "description": "Build a new plan even if one from the last 30 days exists ($12). Default false.",
+  "type": "boolean"
+}
    • removedInput schema / properties / stakeholders
      Removed value: -{
-  "description": "Known stakeholders at the account",
-  "items": {
-    "properties": {
-      "name": {
-        "type": "string"
-      },
-      "role": {
-        "description": "Buying committee role (champion, economic_buyer, etc.)",
-        "type": "string"
-      },
-      "title": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
  4. First observedv1.4.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare write-like, open-world, non-destructive behavior, and the description adds substantial context beyond that: it is paid, takes 1–3 minutes, returns a job_id for later retrieval via get_asset, returns a link with a short summary, and reuses plans from the last 30 days unless refreshed. It also sets a caution that the committee and champion should be treated as a map to confirm with each person. No contradiction with annotations.

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?

The description is front-loaded with the usage condition, then proceeds through output, caching, latency, payment, and follow-up in a logical sequence. Every sentence contributes operational detail; there is no filler.

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?

For a complex, paid, asynchronous, open-world tool with no output schema, the description covers what the agent needs: when to invoke, what the output looks like, how long it takes, how to retrieve it, how caching affects behavior, and the payment prerequisite. Nothing essential is missing.

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 description coverage is 100%, so the schema already defines all six parameters. The description still adds meaningful workflow context around quoteId and maxAmountCents by telling the agent to check the price with quote before running, and it implies the caching behavior tied to the refresh parameter. That extra guidance lifts it above the baseline 3.

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?

The description states a specific verb and resource: it builds an account plan for a target account. It enumerates the concrete contents of that plan — buying committee map, fit opportunities, likely champion, messaging, next steps — so an agent can distinguish it from generic asset or brief tools without opening the schema.

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 description gives a clear condition: 'Use this when the person wants a plan for a specific target account.' It also explains the cached-result behavior and a prerequisite workflow (check price with quote, then call get_asset with the job_id). It stops short of naming when-not-to-use or an explicit sibling alternative for a different task, so it is strong but not exhaustive.

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