Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

match_prices_and_generate_rfq

Matches BoQ items to regional unit-price databases, flags transport-sensitive items, builds ready-to-apply pricing payloads, and groups materials into six supplier RFQ packages for procurement.

Instructions

[v0.4 Tool 15] Match BoQ items against regional unit-price databases (Tier 1 own regional DB,
Tier 2 supplier catalogs, Tier 3 built-in benchmarks), flag transport-sensitive items, produce
ready-to-apply `BoQRowPricingInput` payloads, and group materials into 6 supplier RFQ packages.

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": {
      "boq_xlsx_path": "<boq_xlsx_path>"
    },
    "name": "match_prices_and_generate_rfq"
  }
}

Input Schema

NameRequiredDescriptionDefault
round_stepNoRounding step for unit prices (0.01 default for EUR/USD; pass 10.0 for HUF).
sheet_namesNoOptional list of visible worksheet names to price.
database_dirNoOptional directory containing `sajat_egysegar_torzs.json` and `partner_es_alvallalkozo_torzs.json`.
boq_xlsx_pathYesAbsolute path to the BoQ Excel workbook (.xlsx / .xlsm).
markup_factorNoGlobal multiplier applied to matched unit prices (e.g., 1.0 for base, 1.20 for +20% markup).
project_locationNoProject city/settlement for regional price routing (e.g., 'Foktő', 'Kecskemét', 'Vecsés', 'Tótkomlós').Kecskemét

Output Schema

NameRequiredDescriptionDefault
boq_pathYes
warningsNo
rfq_packagesNo
matched_recordsNo
resolved_regionYes
project_locationYes
matched_rows_countYes
ready_row_pricingsNo
total_rows_processedYes
unmatched_rows_countYes
markup_factor_appliedYes
estimated_grand_total_netYes
transport_sensitive_rows_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 supplied, the description must carry the behavioral burden, and it does add real value by disclosing the three-tier matching strategy (own regional DB, supplier catalogs, built-in benchmarks) and the transport-sensitivity flagging step. It does not state whether the tool only reads the workbook or writes files, what happens to items with no price match, or whether missing database files cause failure. Those gaps matter for a file-consuming pipeline tool.

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?

It is a single front-loaded sentence covering four distinct operations, so it is dense but readable. The '[v0.4 Tool 15]' prefix is internal bookkeeping that consumes attention without informing tool selection, and packing multiple outputs into one clause makes the sentence harder to scan than a short structured list would be.

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-value documentation is not required. However, for a multi-stage tool with file input, optional database directory dependency, and no annotations, the description omits whether outputs are written to disk, how unmatched items are handled, and whether the RFQ grouping is deterministic. Those are the missing pieces an agent needs before invoking it on a real workbook.

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%, so every parameter (round_step, markup_factor, project_location, database_dir, sheet_names, boq_xlsx_path) is already documented with examples and defaults. The description adds no parameter-level detail beyond implying that project_location drives the 'regional' routing. 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 chain and resource: match BoQ items against three tiers of unit-price databases, flag transport-sensitive items, emit BoQRowPricingInput payloads, and produce 6 RFQ packages. An agent knows exactly what the tool does end-to-end. It stops short of 5 because it never distinguishes this from the closest sibling, apply_boq_modifications_and_pricing, which an agent must also decide between.

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 when-to-use / when-not-to-use guidance and no mention of the pipeline position relative to siblings (e.g., run this before apply_boq_modifications_and_pricing). The only usage signal is implicit in the tier wording. Prerequisites such as needing a BoQ workbook and possibly a database directory are not stated.

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