Software Estimation MCP

Calculate Quotation

calculate_quotation

Calculate direct costs, overhead, margin-based sale price, and taxes from project hours and hourly rates to generate accurate software project quotes.

Instructions

Calcula costo directo, overhead, precio basado en margen sobre venta e impuesto indicado.

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": {
      "total_hours": "<total_hours>",
      "hourly_rate_cost": "<hourly_rate_cost>"
    },
    "name": "calculate_quotation"
  }
}

Input Schema

Name	Required	Default
`currency`	No	PEN
`total_hours`	Yes
`tax_rate_pct`	No
`hourly_rate_cost`	Yes
`overhead_percentage`	No
`target_profit_margin_pct`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 21, 2026

TDQS

B3.2/5.0

Behavior3/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. It does disclose the computation chain (direct cost → overhead → margin-based price → tax), which is real behavioral content. However, it never states that this is a pure, non-mutating calculation with no persistence, nor how currency or defaults (PEN, 15% overhead, 30% margin) affect the result.

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 dense sentence that front-loads the core computation and lists the derived values in calculation order. Nothing is wasted, though the total absence of usage context makes it under-specified rather than optimally concise.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. Against that, 0% parameter coverage, no annotations, and no usage context leave the agent guessing about the currency input and when this tool belongs in the workflow.

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

Parameters3/5

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

Schema description coverage is 0% across 6 parameters, so the description must compensate. It conceptually names four of the inputs (hours×rate as direct cost, overhead percentage, target margin, tax rate) but omits 'currency' entirely and gives no units or format for any of them.

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 ('Calcula') and enumerates the exact quantities produced: direct cost, overhead, margin-based sale price, and tax. An agent knows precisely what computation this performs. It does not differentiate itself from the closest sibling, generate_quote_pdf, which presumably consumes this output.

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 call this versus alternatives, no prerequisites, and no mention of the quote-generation siblings. The agent must infer that this is the numeric engine that feeds generate_quote_pdf.

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

Deploy Server