Skip to main content
Glama

construction_materials_cpr_audit

Read-onlyIdempotent

[Deterministic CPR construction material compliance. Pure calculation, read-only, side-effect free]. Audits Declaration of Performance and Conformity (DoP&C) under Construction Products Regulation CPR (EU) 2024/2773 and harmonized EN standards (EN 10025, EN 206, EN 771, EN 13162), verifies AVCP System & Notified Body (NANDO), and benchmarks EPD Global Warming Potential (GWP A1-A3). Usage: Use this tool to verify CE marking eligibility and environmental performance for structural steel, concrete, bricks, and insulation. Returns: JSON object with { isDoPCompliant: boolean, ceMarkingPermitted: boolean, standardVerification: object, avcpVerification: object, environmentalBenchmarking: object }.

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": {
      "materialCategory": "<materialCategory>",
      "dopNumber": "<dopNumber>",
      "manufacturerName": "<manufacturerName>",
      "harmonizedStandard": "<harmonizedStandard>",
      "avcpSystem": "<avcpSystem>",
      "intendedUse": "<intendedUse>",
      "declaredPerformance": "<declaredPerformance>"
    },
    "name": "construction_materials_cpr_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
epdDataNoEPD Global Warming Potential module A1-A3 data
dopNumberYesDeclaration of Performance (DoP) identifier
avcpSystemYesAVCP verification system
intendedUseYesIntended structural or insulation use
manufacturerNameYesLegal name of the manufacturer
materialCategoryYesConstruction material family
harmonizedStandardYesHarmonized standard (e.g. EN 10025-2, EN 206, EN 771-1, EN 13162)
notifiedBodyNumberNo4-digit EU Notified Body NANDO code
declaredPerformanceYesDeclared technical performance values

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the bracketed tag 'Pure calculation, read-only, side-effect free' largely restates them rather than adding new disclosure. It does add the useful traits of determinism and pure calculation (fixed inputs imply fixed outputs), but says nothing about whether NANDO/notified body data is looked up live, how failures or unknown NANDO codes are handled, or validation rules tying AVCP system to required notified body.

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?

Front-loaded with the core purpose, then a Usage line and a Returns line with an explicit field list - an effective structure for an agent. The bracketed annotation restatement is mild redundancy, and the standards list could be trimmed without loss.

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 9-parameter, nested-object tool with no output schema, the explicit return-field list is valuable and largely compensates. However, the description omits how conditional parameters behave (notifiedBodyNumber vs avcpSystem), what inputs cause a non-compliant verdict, and whether external NANDO data is queried - gaps an agent would need before calling.

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

Parameters2/5

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

Schema description coverage is 100% and the schema already documents every parameter with descriptions, enums and examples, so 3 is the baseline. The description adds little mapping between parameters and the verification steps beyond naming the concepts (AVCP, NANDO, GWP A1-A3); it does not clarify conditional logic, e.g. why notifiedBodyNumber is optional or which AVCP systems require it.

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 opens with a specific verb+resource pair ('Audits Declaration of Performance and Conformity (DoP&C) under Construction Products Regulation') and enumerates the concrete checks performed (AVCP System, Notified Body NANDO, EPD GWP A1-A3). It never names or contrasts the sibling tools, but the construction-materials/CPR domain is narrow enough that an agent can place it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Use this tool to verify CE marking eligibility and environmental performance for structural steel, concrete, bricks, and insulation,' which gives a clear trigger and scope. It stops short of naming alternatives or stating when-not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources