resolve_assembly_from_description
Resolve a plain-English job description to candidate catalogue assemblies and the fields you'll need to compute one. Deterministic router — it does NOT return a Bill of Quantities and NEVER guesses parameter values; it returns candidate slugs (plural when ambiguous, with clarifying questions), ea...
This record as markdown: /tools/com-civilquants-civilquants/resolve-assembly-from-description.md
What resolve_assembly_from_description does on Civilquants
AI agents call resolve_assembly_from_description to retrieve information from Civilquants without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
description | string | Yes | |
preferred_standard | object | — | |
return_resolution_log | boolean | — |
Parameters from the server's own tool schema.
Why resolve_assembly_from_description is rated Low
The tool purely resolves/queries a catalogue based on a plain-English description and returns metadata (candidate slugs, field definitions, clarifying questions). It has no side effects, does not execute computations, and explicitly states it does not return a Bill of Quantities or guess values. This is a read/lookup operation with low blast radius.
From the tool's definition Deterministic router — it does NOT return a Bill of Quantities and NEVER guesses parameter values; it returns candidate slugs... and per-field metadata
Attacks that exploit this kind of access
The rule that runs resolve_assembly_from_description safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Civilquants, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resolve_assembly_from_description, this is the rule to start with:
resolve_assembly_from_description is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Civilquants, apply this rule, and every resolve_assembly_from_description call is checked against it from then on.
Questions about resolve_assembly_from_description
Resolve a plain-English job description to candidate catalogue assemblies and the fields you'll need to compute one. Deterministic router — it does NOT return a Bill of Quantities and NEVER guesses parameter values; it returns candidate slugs (plural when ambiguous, with clarifying questions), each assembly's tier, whether it supports compute_multi_section_assembly, and per-field metadata (unit, min/max, default). Then call compute_<slug> (or compute_multi_section_assembly) with the values you fill in. Also known as compute_from_description. Example: {"description":"a 3 m deep manhole","preferred_standard":"MMHW"}. It is categorised as a Read tool in the Civilquants MCP Server, which means it retrieves data without modifying state.
resolve_assembly_from_description accepts 3 parameters: description, preferred_standard, return_resolution_log. Required: description. The full parameter table on this page comes from the server's own tool schema.
Register the Civilquants MCP server in PolicyLayer and add a rule for resolve_assembly_from_description: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Civilquants. Nothing to install.
resolve_assembly_from_description is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the resolve_assembly_from_description rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for resolve_assembly_from_description. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
resolve_assembly_from_description is provided by the Civilquants MCP server (https://api.civilquants.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Civilquants, and thousands of servers like it.
This server
Across the catalogue