Skip to main content
Glama

estimate_textile_impact

Read-onlyIdempotent

Use this tool to estimate the environmental and regulatory profile of textile/fashion products from their fibre composition (plus category, country, optional weight): CO2e per unit with factor sources (Base IMPACTS/PEF), water use, synthetic share, French microfibre notice, PFAS check flag, forced-labour risk by country and an EPR fee estimate. Up to 200 products. Deterministic screening estimates, no account needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "estimate_textile_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNoA single product.
productsNoProducts with composition (e.g. '80% cotton, 20% polyester'), category, country, optional weight_kg.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the description's job is to add context — and it does, by framing results as deterministic screening estimates rather than certified LCA, disclosing the 200-product cap, and confirming no account is required. It does not say what happens with invalid composition strings or partially valid batches, which keeps it below a 5.

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 definition is front-loaded with the action and followed by a compact inventory of outputs and limits, with no filler sentences. The output enumeration is a long run-on list that could be trimmed since a return schema exists, but no sentence is misleading or wasted.

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?

For a read-only screening estimator with an output schema, the description covers the input basis, batch limit, determinism caveat and the class of metrics returned. The main remaining gap is the shape of entries inside the loosely typed product objects, which the description only partially compensates for.

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 the baseline is 3; the schema already documents both the single 'product' and the 'products' array with maxItems 200. The description does add useful meaning by naming the fields expected inside each product object (composition, category, country, optional weight_kg), but the nested objects themselves are untyped empty objects, so this is a modest supplement rather than compensation.

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 opens with a specific verb and resource ('estimate the environmental and regulatory profile of textile/fashion products') and then enumerates exactly what is computed — CO2e per unit with factor sources, water use, synthetic share, French microfibre notice, PFAS flag, forced-labour risk, EPR fee. An agent can distinguish this from the DPP/document siblings without opening the schema.

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?

It states the input basis (fibre composition plus category, country, optional weight) and operating context ('deterministic screening estimates, no account needed'), which tells the agent this is a low-friction screening call. It does not name an alternative tool or state when not to use it, so it falls short of explicit routing guidance.

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