Skip to main content
Glama
HPT-SU

hptsu MCP server

Official
by HPT-SU

search_zotts

Search vehicle conformity assessment conclusions by number, VIN, brand, or other parameters to retrieve compliance documents from the Russian/EAEU registry.

Instructions

Search ЗОТТС (vehicle conformity assessment conclusion).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vinNoVIN substring.
pageNo1-based page index.
typeNoType.
brandNoBrand.
issuerNoCertification body name — auto-resolved to id (or pass numeric id).
numberNoЗОТТС number.
categoryNoVehicle category.
eco_classNoEcological class — '5' or name; auto-resolved to reference id.
page_sizeNoRows per page (max 50).
axis_countNoAxle count (e.g. '2') or exact 'axes / wheels' (e.g. '2 / 4') — auto-resolved to reference id. A bare axle count may match several wheel configs; then candidates are returned to pick from.
wheel_formulaNoWheel formula (e.g. '4x2'); auto-resolved to reference id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, and the description lacks any behavioral details (e.g., read-only, pagination, return format). Only says 'Search', which is insufficient for an agent to understand side effects or constraints.

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?

A single short sentence is concise and front-loaded with the key information. However, it may be too terse, but it avoids redundancy.

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

Completeness2/5

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

Given the complexity of 11 parameters and the presence of many sibling tools, the description is too minimal. It does not explain the tool's role or when to use it, leaving gaps for an agent.

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 parameters are fully documented in the schema. The description adds no extra meaning beyond what is already in the schema, meeting the baseline for high coverage.

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?

Description states 'Search ЗОТТС (vehicle conformity assessment conclusion)', clearly indicating the action and resource. However, it does not differentiate from sibling search tools like search_otts or search_certificates.

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?

No guidance on when to use this tool versus alternatives. Sibling tools include many similar searches, but the description offers no context for selecting this one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HPT-SU/hptsu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server