Skip to main content
Glama
HPT-SU

hptsu MCP server

Official
by HPT-SU

search_zoets

Search vehicle technical expertise conclusions (ЗОЕТС) in the hpt.su registry using number, VIN, brand, or other criteria to retrieve compliance documents.

Instructions

Search ЗОЕТС (vehicle technical expertise conclusion).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vinNoVIN (10-17 chars).
pageNo1-based page index.
typeNoType.
yearNoManufacture year.
brandNoBrand.
motorNoElectric motor model.
engineNoICE engine model.
issuerNoTesting lab name — auto-resolved to id (or pass numeric id).
numberNoЗОЕТС number.
date_toNoIssue date to (YYYY-MM-DD).
categoryNoVehicle category.
comm_nameNoCommercial name.
date_fromNoIssue date from (YYYY-MM-DD).
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.
motor_powerNoMotor power (kW).
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?

With no annotations provided, the description carries the full burden of behavioral disclosure. However, it only states the action ('Search') without revealing any behavioral traits such as idempotency, read-only nature, rate limits, or side effects.

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 description is a single sentence, making it concise. However, it is too brief given the complexity of the tool (18 parameters); it could include more contextual information without losing conciseness.

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?

The description lacks essential context for a search tool with many optional parameters and an output schema. It does not explain how the search works, the significance of the results, or how parameters interact. The presence of an output schema mitigates the need to explain return values, but other aspects are 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 coverage is 100%, and each parameter already has a description in the schema that explains its meaning. While some descriptions (e.g., axis_count, issuer) provide extra context about auto-resolution, the tool description does not add significant value beyond what the schema offers.

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 clearly states the tool searches for 'ЗОЕТС (vehicle technical expertise conclusion)', providing a specific resource. However, it does not distinguish this from sibling tools like search_otts or search_certificates, which have similar naming patterns.

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 is provided on when to use this tool versus alternatives. All parameters are optional, but there is no mention of typical use cases, prerequisites, or when not to use this tool.

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