Skip to main content
Glama

critical_raw_materials_screener

Read-onlyIdempotent

[Deterministic CRMA supply chain risk screener. Pure calculation, read-only, side-effect free]. Screens product Bill of Materials (BOM) against the 34 EU Critical and 17 Strategic Raw Materials under Regulation (EU) 2024/1252, auditing single third-country concentration against the statutory 65% import dependency cap. Usage: Use this tool to audit supply chain exposure to Lithium, Cobalt, Rare Earths, Gallium, and other critical minerals. Returns: JSON object with { totalCriticalMaterialsMassGrams: number, criticalMassPercentage: number, strategicMaterialsCount: number, materialsProfiles: array, crmaGeopoliticalRiskRating: string, crma2030DiversificationCompliance: boolean }.

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": {
      "billOfMaterials": "<billOfMaterials>"
    },
    "name": "critical_raw_materials_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
billOfMaterialsYesBill of Materials component list
totalProductWeightGramsNoTotal product weight in grams

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so 'read-only, side-effect free' is mostly redundant. However, the description does disclose behavior beyond annotations: the deterministic calculation model, the statutory 65% concentration threshold being audited, and an explicit enumeration of return fields including crmaGeopoliticalRiskRating and crma2030DiversificationCompliance.

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?

The bracketed header, Usage line, and Returns line are front-loaded and easy to scan, and the return-field enumeration is genuinely useful given there is no output schema. Minor waste in repeating the annotation-derived 'read-only, side-effect free' claim.

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

Completeness4/5

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

With no output schema, the description compensates by listing the returned JSON fields, and the input schema is fully self-documenting. The only gaps are edge behavior such as what happens with an empty BOM or what the optional totalProductWeightGrams defaults to when omitted.

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 both parameters and every nested BOM field are already documented with examples (Lithium, Cobalt, Neodymium, Gallium). The description adds no syntax or constraint detail beyond mentioning the BOM, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: screening a product Bill of Materials against the 34 EU Critical and 17 Strategic Raw Materials under Regulation (EU) 2024/1252. The regulated scope (65% single third-country import dependency cap) makes it unmistakable and clearly distinct from the sibling audits covering construction materials, DPP payloads, and green claims.

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

Usage Guidelines3/5

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

The 'Usage' line gives a use case ('audit supply chain exposure to Lithium, Cobalt, Rare Earths, Gallium'), but it largely restates the purpose rather than routing between tools. There are no exclusions, no stated prerequisites (e.g. that a complete BOM with supplier countries is required), and no named alternative for adjacent compliance checks.

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