hptsu-mcp

search_otts

Search ОТТС (vehicle type approvals, ТР ТС 018/2011).

Input Schema

TableJSON Schema

Name	Required	Description
`vin`	No	VIN, full or partial (5-17 characters).
`mods`	No	Modifications, full or partial.
`page`	No	1-based page index.
`type`	No	Vehicle type / model, full or partial.
`brand`	No	Vehicle brand (e.g. 'Toyota').
`issuer`	No	Certification body name — auto-resolved to id (or pass numeric id). See list_certification_bodies.
`number`	No	ОТТС number, full or partial.
`chassis`	No	Chassis identifier, full or partial.
`category`	No	Vehicle category (M1, N2, L3, …).
`comm_name`	No	Commercial name, full or partial.
`eco_class`	No	Ecological class — pass '5' or the 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.
`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.

Changed5 schema fields changedJul 15, 2026

changedInput schema / properties / chassis / description

Previous value: -"Chassis identifier (icontains)."New value: +"Chassis identifier, full or partial."

changedInput schema / properties / comm_name / description

Previous value: -"Commercial name (icontains)."New value: +"Commercial name, full or partial."

changedInput schema / properties / mods / description

Previous value: -"Modifications (icontains)."New value: +"Modifications, full or partial."

changedInput schema / properties / type / description

Previous value: -"Vehicle type / model (icontains)."New value: +"Vehicle type / model, full or partial."

changedInput schema / properties / vin / description

Previous value: -"VIN substring (5-17 chars) — backend autoroute substring/DAWG."New value: +"VIN, full or partial (5-17 characters)."

First observedJul 12, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations provided, so the description carries the full burden. It does not disclose whether the tool is read-only, requires special permissions, or describes any side effects. The pagination parameters exist but their behavior is not summarized.

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 very short (one sentence), which is concise but lacks necessary detail. It is not wasteful, but also not fully helpful.

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?

With 14 parameters and an output schema, the description should explain return values or behavior. It does not. The input schema is well covered, but contextual completeness is low due to missing output/behavioral context.

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 description adds little beyond the schema. Baseline is appropriate at 3.

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

Purpose5/5

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

Description clearly states it searches for OTTS (vehicle type approvals under TR TS 018/2011). The verb 'Search' and resource 'OTTS' are specific, and the regulation reference distinguishes it from other search tools like search_certificates or search_declarations.

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 siblings or any prerequisites. The description is a single sentence with no context about alternatives or exclusions.

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.