Skip to main content
Glama

Drict

List a country's label requirements

list_requirements
Read-only

What the label law of a country asks a product's label to carry, before a label exists: the mandatory items, the items needed only in some cases, the language rule and what to check by eye, each with its law and the official sources. Use it to write or brief a label; use check_label to check one.

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": {
      "country": "<country>"
    },
    "name": "list_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesWhere the product is sold: a code from list_markets.
productNo"food", "cosmetics", "goods", "devices", "supplements", "alcohol", "petfood", "battery", "electrical", "chemical", "toy", "textile" or a product code from list_markets. Defaults to food.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the payload includes per-item legal citations and official sources, and it applies "before a label exists" — i.e., it is a static reference lookup, not a per-product compliance verdict. It does not describe output shape or how gaps/unsupported combinations are reported, which is the remaining gap.

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?

Two sentences, purpose front-loaded, with the routing guidance last — a sensible order and no filler. The first sentence is dense and slightly list-heavy, but each clause (mandatory vs conditional items, language rule, eye-check items, citations) carries information the agent needs.

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 must carry the return-value burden, and it largely does by naming the four requirement categories and their legal sourcing. Parameters are fully covered by the schema and safety is covered by annotations. What is missing is how the response is shaped or how unsupported country/product pairs behave, which is minor for a read-only reference tool.

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%, with the country enum documented as "a code from list_markets" and product documented with an enumerated list plus a stated default of food. The description adds no parameter-level meaning of its own, so the baseline 3 applies — the schema does all the work here.

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 concrete resource (a country's label law requirements) and enumerates what it returns: mandatory items, conditional items, the language rule, eye-check items, each with its law and official sources. This is specific enough to distinguish it from check_label, which validates an existing label, without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use ("Use it to write or brief a label") and names the alternative with its selecting condition ("use check_label to check one"). The pre-label timing constraint is also stated up front, so the agent knows this is reference lookup rather than validation.

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.