Skip to main content
Glama

analyze_supply_chain

Read-onlyIdempotent

Use this tool to analyse a fashion/textile supply base from product data (supplier, country of manufacture, composition, facility id): per-supplier data scores, country shares, country concentration index (HHI), fibre mix and data-quality gaps that block traceability and DPPs. Up to 200 products. Deterministic, no account needed.

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": {
      "products": "<products>"
    },
    "name": "analyze_supply_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYesProducts with supplier, country, composition and optional facility_id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds genuinely new traits beyond them: results are deterministic and no account or credentials are required, which tells an agent the call is safe to repeat and free of auth setup. It does not contrast with any annotation.

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?

It is a single dense sentence with the purpose front-loaded and the operational constraints (200 cap, deterministic, no account) placed at the end where they belong. No filler, though the parenthetical field list is somewhat redundant with the schema and lengthens an already long sentence.

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

Completeness5/5

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

Given an output schema exists, the description needn't explain return values, and it still gestures at them via the named metrics. Scope, input limit, determinism and auth-freedom are all stated, and annotations carry the safety profile, leaving nothing an agent needs in order to call this correctly.

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 coverage is 100% and the schema already describes the products array with its fields and maxItems of 200, so the premise is documented. The description only restates the same field list (supplier, country, composition, facility id) and the same cap, adding no format, nullability or validation meaning beyond the schema.

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 and resource ('analyse a fashion/textile supply base from product data') and enumerates the concrete outputs: per-supplier scores, country shares, HHI concentration, fibre mix and data-quality gaps. That makes the tool's function unmistakable and clearly distinct in character from the DPP-building siblings, though no sibling is named explicitly.

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 opening 'Use this tool to analyse...' plus the input shape implies the trigger condition (you have product records with supplier/country/composition and want aggregate insight) and the 200-product cap hints at batch scale. However there are no exclusions, no prerequisites, and no routing advice toward alternatives such as estimate_textile_impact or validate_dpp_readiness.

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