Skip to main content
Glama
HPT-SU

hptsu MCP server

Official
by HPT-SU

search_sbkts

Search for vehicle safety certificates (СБКТС) by number, VIN, brand, or other criteria to verify compliance with EAEU regulations.

Instructions

Search СБКТС (vehicle safety certificate).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vinNoVIN (10-17 chars; substring/exact).
pageNo1-based page index.
typeNoType.
yearNoManufacture year (YYYY).
brandNoBrand.
motorNoElectric motor model (icontains).
engineNoICE engine model (icontains).
issuerNoTesting lab name — auto-resolved to id (or pass numeric id). See list_test_labs.
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
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits like pagination, filtering logic, or result format. For a search tool with 18 parameters, this is a significant omission.

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

Conciseness2/5

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

The description is extremely short (one sentence), but it is under-specified rather than efficient. Essential information about usage and behavior is missing.

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

Completeness1/5

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

Given 18 parameters and no annotations, the description is severely incomplete. It omits details about output format, pagination, auto-resolution of parameters, and error handling.

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% with detailed parameter descriptions, so the baseline is 3. The tool description adds no additional semantic meaning beyond what's in the schema, so it stays at 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool searches for vehicle safety certificates (СБКТС), which is clear but fails to distinguish it from sibling tools like search_certificates or search_declarations that also search for certificate types.

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 such as search_declarations or search_otts. The description lacks any context for tool selection.

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