Software Estimation MCP

Generate Action Plan Pdf

generate_action_plan_pdf

Turn project roadmap data into a PDF action plan with schedule, actions, dependencies, and success criteria.

Instructions

Genera plan de acción PDF con cronograma, acciones, dependencias y criterios de éxito.

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": {
      "client_name": "<client_name>",
      "project_title": "<project_title>",
      "roadmap_data": "<roadmap_data>"
    },
    "name": "generate_action_plan_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`file_name`	No
`client_name`	Yes
`action_items`	No
`dependencies`	No
`roadmap_data`	Yes
`project_title`	Yes
`success_criteria`	No
`decisions_required`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 21, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about side effects: whether a file is written to disk, where it is stored, whether it is overwritten, or if a path/URL is returned. The only behavioral fact is the output format (PDF), which is already in the name.

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?

A single front-loaded sentence with no filler; the artifact and its contents come first. Brevity here is efficient, though it is brevity at the cost of coverage.

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 an 8-parameter tool with nested objects and no annotations, the description is thin. An output schema exists so return values need not be explained, but the agent gets no help on required inputs, the structure of roadmap_data, or the tool's side effects.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters including nested objects, and the description only loosely maps to four of them (roadmap_data as 'cronograma', action_items, dependencies, success_criteria). It says nothing about file_name, client_name, project_title, or decisions_required, nor about the shape of roadmap_data.

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?

States a specific verb and resource ('Genera plan de acción PDF') plus the content it packages (cronograma, acciones, dependencias, criterios de éxito), so an agent knows exactly what artifact it produces. It does not differentiate itself from the sibling generate_action_plan_markdown, which is the only meaningful ambiguity.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this over generate_action_plan_markdown, generate_proposal_pdf, or render_markdown_pdf. Usage is only implied by the PDF output format in the name.

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

Deploy Server