hptsu-mcp

search_sbkts

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

Input Schema

TableJSON Schema

Name	Required	Description
`vin`	No	VIN (10-17 chars; substring/exact).
`fuel`	No	Engine fuel type, one of: 'бензин', 'дизель', 'газ', 'электро', 'водород'.
`page`	No	1-based page index.
`type`	No	Type.
`year`	No	Manufacture year (YYYY).
`brand`	No	Brand.
`motor`	No	Electric motor model, full or partial.
`engine`	No	ICE engine model, full or partial.
`issuer`	No	Testing lab name — auto-resolved to id (or pass numeric id). See list_test_labs.
`number`	No	СБКТС number.
`date_to`	No	Issue date to (YYYY-MM-DD).
`category`	No	Vehicle category.
`comm_name`	No	Commercial name.
`date_from`	No	Issue date from (YYYY-MM-DD).
`eco_class`	No	Ecological class — '5' or name; auto-resolved to reference id.
`page_size`	No	Rows per page (max 50).
`axis_count`	No	Axle 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.
`powertrain`	No	Powertrain type: 'ice' (combustion), 'hybrid', 'electric'.
`motor_power`	No	Motor power (kW).
`wheel_formula`	No	Wheel formula (e.g. '4x2'); auto-resolved to reference id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 30, 2026

addedInput schema / properties / fuel

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Engine fuel type, one of: 'бензин', 'дизель', 'газ', 'электро', 'водород'.",
+  "title": "Fuel"
+}

addedInput schema / properties / powertrain

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Powertrain type: 'ice' (combustion), 'hybrid', 'electric'.",
+  "title": "Powertrain"
+}

Changed2 schema fields changedJul 15, 2026

changedInput schema / properties / engine / description

Previous value: -"ICE engine model (icontains)."New value: +"ICE engine model, full or partial."

changedInput schema / properties / motor / description

Previous value: -"Electric motor model (icontains)."New value: +"Electric motor model, full or partial."

First observedJul 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as pagination behavior, result format, or any side effects. Even with an output schema, the agent needs clues about how the search operates (e.g., concurrency, rate limits, data freshness).

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?

Single, clear sentence that states the tool's purpose. Highly concise and front-loaded, though could benefit from a brief note on common use cases or return value summary.

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

Completeness3/5

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

With 20 parameters, an output schema, and no required fields, the description is minimally adequate. However, it lacks examples, parameter interaction guidance (e.g., AND vs OR logic), and any mention of how to handle large result sets beyond pagination parameters.

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 descriptions for each parameter, including auto-resolution behavior for some fields (e.g., issuer, eco_class, axis_count). The tool description itself adds no extra parameter context beyond the schema, which is acceptable given full 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 clearly states the tool searches for vehicle safety certificates (СБКТС), which is a specific document type. This distinguishes it from sibling tools like search_certificates or search_declarations, though it could be more explicit about the search scope.

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 (e.g., search_certificates, search_declarations). No mention of prerequisites, parameter combination logic, or when not to use it. Agents lack context for proper tool selection.

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

All hptsu-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.