bluecolumn-mcp

call_prepare

Retrieve customer memory context before a voice call, including memories, relationship summary, unresolved items, and suggested opening to personalize interactions.

Instructions

NEW (Audio Intelligence): Get memory context before a voice call starts.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "call_prepare"
  }
}

Input Schema

Name	Required	Description	Default
`include`	No
`customer_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 4, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read-like operation via 'Get', but does not state whether it has side effects, requires specific permissions, or what the returned context contains. This is too minimal to be considered transparent for an unprecedentedly annotated 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?

The core description is a single, front-loaded sentence that clearly states the action and context. However, the 'NEW (Audio Intelligence)' prefix is non-informative noise that wastes tokens; without it, this would be a perfect 5.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, this description is incomplete. It provides purpose and timing but omits parameter behavior, expected output, prerequisites, and any interaction with sibling tools, leaving significant gaps for an agent trying to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention customer_id or include at all. While the schema's enum values hint at the include options, the description adds no meaning to the parameters, forcing the agent to infer how to use them from names alone.

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 uses a specific verb 'Get' and resource 'memory context', with a clear temporal scope 'before a voice call starts' that distinguishes it from siblings like call_complete and audio_recall. This directly states the tool's function and intended point in the call lifecycle.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before a voice call starts' implies the usage timing, but it does not explicitly mention alternatives or exclusions. No guidance is given on when not to use this tool or how it compares to sibling tools like recall or audio_ingest, so the usage context is present but not fully developed.

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

Deploy Server