Skip to main content
Glama

Xonta Customs RU

classification_rulings_search

Read-onlyIdempotent

Search EEC (Eurasian Economic Commission) decisions on classification of specific goods.

These decisions are binding for all EAEU customs and are the strongest evidence for a code. Returns the decision number and date, the product, the TN VED code or heading and a source link.

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

Input Schema

NameRequiredDescriptionDefault
codeNoTN VED code or heading, e.g. '9013'
queryNoProduct words, e.g. 'прицел тепловизионный'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely non-structured context: what the records contain (decision number and date, product, TN VED code/heading, source link) and their legal weight for EAEU customs. It stops short of describing matching semantics (partial vs exact, how code and query combine).

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 short sentences, front-loaded with the purpose, then the authority of the evidence, then the return shape. No filler and no restatement of the tool name.

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 usefully enumerates the returned fields, which is exactly what an agent needs to decide whether to rely on it. The remaining gap is search behavior for a zero-required-parameter tool — whether an empty call returns everything or errors is unstated.

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% and both parameters already carry examples ('9013', 'прицел тепловизионный'), so the schema does the heavy lifting. The description adds nothing about how code and query interact or what happens when both are omitted; 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?

States a specific verb and resource: searching EEC classification decisions for specific goods, and frames the output domain (TN VED code or heading). It does not explicitly contrast with the close siblings tnved_search or tnved_code_info, so an agent must infer that this returns rulings rather than the code directory itself.

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?

'These decisions are binding for all EAEU customs and are the strongest evidence for a code' implies when the tool is valuable (authoritative confirmation of a classification), but no explicit when-to-use/when-not and no alternative is named. With all parameters optional, there is also no guidance on whether to call it with a code, a query, both, or neither.

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.