Skip to main content
Glama

Drict

Check a label against a country's label law

check_label
Read-only

Check the printed text of a product label against the label law of the country where it is sold. Returns the points to check: each mandatory item found or not found, items needed only in some cases, missing languages, and what to check by eye — each with the law it comes from and, where known, the official text. Key-word check only: not legal advice, never a statement that the label is compliant.

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>",
      "text": "<text>"
    },
    "name": "check_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesEvery line printed on the label, one per line, in the language(s) printed.
countryYesWhere the product is sold: a code from list_markets (us, uk, eu, kr, hk, cn, jp, vn…).
productNoWhat the product is: "food" (food and drinks), "cosmetics", "goods" (other consumer goods), "devices" (medical devices: us, eu, fr, es, cy, uk, kr), "supplements", "alcohol", "petfood", "battery", "electrical", "chemical", "toy", "textile" (where the country has them), or a product code from list_markets. Defaults to food.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses the return structure (found/not-found mandatory items, conditional items, missing languages, visual checks, each with its legal source and official text where known). It also discloses the fundamental behavioral limit that matching is keyword-based and never asserts compliance, which is exactly the kind of caveat annotations cannot convey and is consistent with openWorldHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the purpose, then the shape of the output, then the guardrail caveat. No redundant restatement of the title and no filler.

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 carries the return-value explanation and does so well, including provenance and confidence limits. It could say more about what happens for markets or product types that are not covered, but nothing essential to invoking it correctly is missing.

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 country, text, and product are already documented, including the enum source (list_markets) and the food default. The description adds nothing about parameter format or edge cases (e.g., unsupported product/country combinations) beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource: check the printed text of a product label against the label law of the country where it is sold. An agent immediately knows what comes in and what comes out. It does not name or distinguish itself from the sibling listing tools (list_markets, list_requirements), so it stops short of a 5.

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?

Usage context is stated clearly: apply it to label text for a specific market, and the explicit scope limit 'Key-word check only: not legal advice, never a statement that the label is compliant' tells the agent what this tool must not be used to conclude. There is no explicit routing to or exclusion of the sibling tools, so no 5.

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.