hptsu-mcp

list_document_files

List the files attached to a document.

Returns `[{file_uid, file_name, kind, pages_count, published_at}]` —
each entry's `file_uid` can be passed to `download_document_file`.

A document often has several PDFs (e.g. cleaned + original); use this
tool to enumerate them and pick the right one before download.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes	One of: otts, otch, zotts, zotch, sbkts, zoets, sout, cert, decl. Slug isn't globally unique between kinds, so kind is required.
`document_slug`	Yes	Document slug (from search.slug field).

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?

Without annotations, the description discloses the return format and how the output connects to another tool. It does not mention pagination, rate limits, or authorization, but for a read-only list operation, the provided information is sufficient and transparent.

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 very concise: two sentences and a list format. It is front-loaded with the purpose and all sentences are useful. No wasted words.

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?

The description includes the purpose, usage hints, and a sample return structure. With an output schema present, it does not need to detail all fields. It covers the essential information for a list tool.

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?

The input schema has 100% coverage with descriptions for both parameters. The description does not add additional meaning beyond what the schema provides, so 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 'List the files attached to a document' with a specific verb and resource. It distinguishes itself from the sibling 'download_document_file' by indicating that this tool is for enumeration before download.

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 provides context for when to use the tool: 'use this tool to enumerate them and pick the right one before download.' It implies use before download, but does not explicitly mention when not to use or contrast with other siblings. Still, it offers clear guidance.

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.