Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

apply_boq_modifications_and_pricing

Writes unit prices, red-bold quantity changes, supplemental K-tétel items, and '-'/'+' variation pairs into an Excel BoQ, updating SUM ranges, cached XML values, and removing calcChain.

Instructions

[v0.3 Tool 11] Safely write unit prices (with optional markup_factor), red-bold quantity modifications,
supplemental K-tételek, and '-'/'+' kiv. észrevétel pairs into an Excel BoQ workbook while updating
SUM ranges, XML `<v>` cached values, and stripping `xl/calcChain.xml`.

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": {
      "source_xlsx_path": "<source_xlsx_path>",
      "output_xlsx_path": "<output_xlsx_path>"
    },
    "name": "apply_boq_modifications_and_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
round_stepNoRounding step for unit prices after markup (default 0.01 for EUR/USD/GBP; pass 10.0 for HUF).
row_pricingsNoList of unit prices and optional quantity/note modifications for existing rows.
markup_factorNoGlobal multiplier applied to unit prices (e.g., 1.0 for base, 1.20 for +20% markup).
output_xlsx_pathYesAbsolute path where the modified and priced BoQ Excel file will be written.
source_xlsx_pathYesAbsolute path to the source BoQ Excel file (.xlsx).
supplemental_itemsNoList of new K-tétel items or '-'/'+' kiv. észrevétel observation pairs to insert.

Output Schema

NameRequiredDescriptionDefault
warningsNo
grand_total_netYes
output_xlsx_pathYes
sheet_net_totalsNo
source_xlsx_pathYes
priced_rows_countYes
calc_chain_removedYes
markup_factor_appliedYes
inserted_k_items_countYes
post_write_formula_anomaliesYes
quantity_modified_rows_countYes
cached_formula_values_updatedYes
inserted_observation_pairs_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose non-obvious side effects: recalculation of SUM ranges, rewriting cached XML `<v>` values, removal of `xl/calcChain.xml`, and red-bold font logging for quantity changes. It still omits whether the source file is left untouched, whether output is overwritten, and what happens on invalid row numbers or sheet names.

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?

The core action is front-loaded, which is good, but the whole definition is a single dense run-on sentence and the '[v0.3 Tool 11]' prefix is internal versioning noise that consumes attention without helping selection. The side-effect list (SUM ranges, calcChain) would read better as a separate sentence.

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?

For a complex mutating tool with no annotations this is reasonably complete on what gets written and what extra files/values get touched, and an output schema exists so return values need not be described. However, prerequisites, validation/error behavior, and whether unrelated workbook content is preserved are all unstated, which is a meaningful gap for a file writer.

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 100% and the nested defs already explain markup_factor, item_mode enum values, and original_row_number in detail. The description only re-summarizes markup_factor and the '-'/'+' pair concept, adding no syntax, units, or edge-case meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a specific verb and resource: writing unit prices, red-bold quantity changes, and K-tétel/kiv. észrevétel rows into an Excel BoQ workbook. That sets it clearly apart from the read/compare/calculate siblings, though it never names an alternative explicitly and opens with the noisy internal tag '[v0.3 Tool 11]'.

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 statement of when to use this versus alternatives, no prerequisites (e.g., audit the source file first, supply pricing data before calling), and no exclusions. The only hint is the word 'Safely', which implies a final write step but leaves the workflow position to inference.

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