Skip to main content
Glama
Sign In
Andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Read your ideal customer profile

get_icp_profile
Read-only

Retrieves the account's Ideal Customer Profile to identify decision-makers, what they are measured on, buying signals, and poor-fit prospects, helping explain who buys and why.

Instructions

Use this when the person asks who their ideal customer is, who isn't a fit, or needs to explain who buys from them and why. Returns the account's ICP, built from what they sell: the buyers who decide, what each one is measured on and the concerns each needs answered, the signals that a company is ready to change, and who isn't a fit. If the first ICP is still being built, it says so; ask again in a minute.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.10
    • removedInput schema / properties / includeAntiPatterns
      Removed value: -{
-  "description": "Include anti-patterns and churn predictors (default: true)",
-  "type": "boolean"
-}
    • removedInput schema / properties / includeSevenAnswers
      Removed value: -{
-  "description": "Include seven critical buyer answers (default: true)",
-  "type": "boolean"
-}
    • removedInput schema / properties / layers
      Removed value: -{
-  "description": "Specific layers to include (1-5). Omit for all layers.",
-  "items": {
-    "enum": [
-      1,
-      2,
-      3,
-      4,
-      5
-    ],
-    "type": "number"
-  },
-  "type": "array"
-}
  2. First observedv1.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=true already covering safety, the description adds non-obvious behavior: the first ICP may still be building, and the agent should ask again in a minute. It also enumerates the returned ICP components, though it does not discuss auth or rate limits.

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?

Three sentences, front-loaded with the usage trigger, followed by the return contents and the retry edge case. Every sentence adds useful information, with no filler or repetition.

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 zero-parameter read-only tool with no output schema, the description supplies the trigger, the returned ICP components, and the eventual-consistency retry behavior. That is enough for an agent to invoke it correctly and interpret the initial empty state.

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?

The tool has zero parameters, so there are no parameter semantics to document. The baseline score for a parameterless tool is 4, and nothing in the description creates ambiguity about inputs.

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?

It states a specific action and resource: returns the account's ICP, scoped to buyers, metrics, concerns, readiness signals, and non-fit accounts. It does not explicitly name sibling tools like get_icp_fit_score or get_persona_profile, but the described output is conceptually distinct enough for an agent to tell what this tool is for.

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 concrete triggers: when the person asks who their ideal customer is, who isn't a fit, or needs to explain who buys from them and why. It does not state when not to use the tool or explicitly point to alternatives among the many sibling tools.

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