Software Estimation MCP

Generate Quote Pdf

generate_quote_pdf

Generate a standalone commercial PDF quote from client, project, hours, scope, and pricing data, separate from the full technical proposal.

Instructions

Genera una cotización comercial PDF independiente de la propuesta técnica completa.

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>",
      "quotation_data": "<quotation_data>",
      "total_hours": "<total_hours>",
      "scope_summary": "<scope_summary>"
    },
    "name": "generate_quote_pdf"
  }
}

Input Schema

Name	Required	Default
`file_name`	No
`assumptions`	No
`client_name`	Yes
`total_hours`	Yes
`out_of_scope`	No
`payment_terms`	No	Por acordar antes de iniciar el trabajo.
`project_title`	Yes
`scope_summary`	Yes
`validity_days`	No
`quotation_data`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 21, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden, yet it says nothing about side effects (writing a PDF file), how file_name is used or whether existing files are overwritten, or what permissions are needed. 'Independiente' conveys scope but no operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single front-loaded sentence with no filler, so it is efficiently written. However, brevity this extreme for a 10-parameter, nested-object tool reads as under-specification rather than disciplined concision.

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

Completeness1/5

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

For a tool with 10 params, 5 required, a nested object, 0% schema coverage, and no annotations, a lone sentence is far from sufficient; an agent cannot know what to pass or what will happen. The existence of an output schema excuses return-value explanation but not the missing input and routing guidance.

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?

Ten parameters (including a nested quotation_data object) with 0% schema description coverage, and the description provides zero parameter meaning — no hint about client_name, total_hours, scope_summary, validity_days, or the shape of quotation_data. Nothing compensates for the total coverage gap.

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+resource ('Genera una cotización comercial PDF') and scopes it as 'independiente de la propuesta técnica completa', which implicitly separates it from the proposal-generation siblings. It never names those siblings explicitly, so differentiation is inferential rather than stated.

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 'independiente de la propuesta técnica completa' implies this is for when only the commercial quote is wanted, not a full proposal — a usable but implicit selection cue. There is no explicit when-to-use/when-not statement and no named alternative (e.g. generate_proposal_pdf, generate_quotation).

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

Deploy Server