Skip to main content
Glama

Drict

List Drict countries

list_markets
Read-only

The 48 countries whose label law Drict checks, each with its code and the products it is checked for (food and drinks, cosmetics, other goods, medical devices, supplements, alcohol, pet food, batteries, electrical goods, chemicals, toys, textiles — where covered; Vietnam has its own eleven).

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": "list_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new context by disclosing the shape of each returned record (code plus checked product categories) in the absence of an output schema. Minor gap: nothing about ordering, size, or the cryptic 'Vietnam has its own eleven' special case.

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

Conciseness3/5

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

The core fact (48 countries, with codes and product coverage) is front-loaded, which is good. The long parenthetical enumerating twelve product categories plus the unexplained Vietnam note bloats a single sentence and pushes the description past what an agent needs to decide to call it.

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 zero-parameter, closed-world reference tool with no output schema, the description is nearly complete: it says what the records contain and what 'coverage' means. The undefined 'Drict' terminology and the unexplained Vietnam clause leave small ambiguities.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline is 4. The description correctly does not invent arguments for a parameterless tool.

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 states a specific resource and scope: the 48 countries whose label law 'Drict' checks, each with a code and covered product categories. An agent can tell this returns static reference data about supported markets. It does not, however, differentiate itself from siblings like list_requirements or check_label, and the term 'Drict' is never defined.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The reader must infer that this is a reference lookup rather than, say, a validation call, purely from the phrase 'The 48 countries...'.

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.