hptsu-mcp

fulltext_search

Full-text search inside type-approval document bodies (PDF text).

Covers ОТТС / ОТШ / ЗОТТС / ЗОТШ. Other document kinds (СБКТС / ЗОЕТС /
СУТ / cert / decl) are not covered by full-text search.

**Premium feature** — requires a plan that includes full-text search
(see https://hpt.su/pricing/) with a subscription covering at least
one type-approval kind.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Filter by registry kind. One of: otts, otch, zotts, zotch. Default: search across all 4 type-approval kinds.
`page`	No	1-based page index.
`query`	Yes	Free-text query (Russian, tsquery-syntax allowed).
`page_size`	No	Rows per page (max 50).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses the premium requirement, which is a behavioral constraint. It does not mention rate limits or performance, but given the nature of the tool, this is acceptable. No contradictions.

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

Conciseness5/5

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

The description is concise with two well-structured paragraphs. The first sentence states the main purpose, followed by specifics and usage notes. No redundant information.

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

Completeness4/5

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

Given the 4 parameters with full schema descriptions, and the output schema existing (though not shown), the description provides sufficient context for an agent to use the tool. It covers scope, limitations, and premium status.

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 each parameter already has a description. The tool description adds context about query being free-text with tsquery-syntax and kind filtering, but does not significantly enhance beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states it performs full-text search inside type-approval document bodies (PDF text), and specifies the covered document kinds (ОТТС, ОТШ, ЗОТТС, ЗОТШ) while excluding others. This distinguishes it from siblings like search_otts and search_zotts which likely search metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly notes when to use (full-text search within covered document kinds) and when not (other document kinds not covered). It also mentions it's a premium feature with a pricing link, providing context for usage. It lacks explicit alternatives but the sibling tools imply metadata searches for other kinds.

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.