CIA Diagnose

action_plan

Read-onlyIdempotent

Turn diagnosis results into a realistic 30/60/90 day roadmap. Prioritize actions by ROI and ease, with DIY or expert-assisted options for each step.

Instructions

Generate a prioritized 30/60/90 day action plan based on diagnosis.

Creates a realistic, phased implementation roadmap. Prioritizes by ROI and ease of implementation. Each action includes DIY option and CIA-assisted option.

Use AFTER business_diagnose to create a roadmap from the results.

Args: company_name: Name of the company. revenue_leak_score: Business Health Score from diagnosis (0-100, HIGHER = healthier). top_dimensions: Comma-separated weakest dimensions from diagnosis (e.g. 'tecnologia, marketing_digital, operaciones'). team_size: Number of employees (affects plan complexity). budget_level: 'low' ($0-500/mo), 'medium' ($500-2000/mo), 'high' ($2000+/mo). lang: Language ('es' or 'en').

Returns: dict: Phased action plan with 30/60/90 day milestones, each containing specific actions, tools, expected outcomes, and DIY vs CIA-assisted options.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "action_plan"
  }
}

Input Schema

Name	Required	Default
`lang`	No	es
`team_size`	No
`budget_level`	No	low
`company_name`	No
`top_dimensions`	No
`revenue_leak_score`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jun 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds that the plan is prioritized by ROI and ease, and that each action includes DIY and CIA-assisted options. No contradictions 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose statement, usage note, and parameter list. It is comprehensive but not overly verbose; however, it could be slightly more concise without losing essential details.

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?

Given the complexity (6 parameters, no schema descriptions), the description thoroughly explains parameters and returns. It mentions the prerequisite of business_diagnose. Minor gaps: no discussion of error handling or rate limits, but annotations cover safety.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the full burden. The description includes a detailed Args section explaining each parameter, including types, defaults, and examples. This adds significant meaning beyond the bare 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?

The description clearly states it generates a prioritized 30/60/90 day action plan based on diagnosis, with specifics like prioritizing by ROI and ease, and including DIY and CIA-assisted options. It distinguishes itself from sibling tools by explicitly stating it should be used after business_diagnose.

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 provides explicit guidance to use AFTER business_diagnose, establishing a clear use case and prerequisite. It does not discuss when not to use or alternative tools, but the context is sufficient for an AI agent to understand the intended workflow.

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

Deploy Server