iit-mcp-hudu

List Assets

hudu_list_assets

Read-only

List one bounded page of Hudu assets across all companies, filterable by company, serial, layout, or search; returns page_size rows and indicates if more pages exist.

Instructions

List ONE bounded page of assets across all companies, backed by the fixed operation assets.listAcrossCompanies. Returns at most page_size rows plus whether more exist; it never pages through the tenant. The operation is page-paginated by the vendor (page and page_size are sent upstream), so later pages are reachable by raising page. This tool takes no operation argument and cannot be redirected to a write. Filter by company_id, primary_serial, asset_layout_id or search. Prefer hudu_get_asset_context to read one asset in full, and hudu_search to find one by text. This is the ungated path for both assets.listAcrossCompanies and the company-scoped assets.list read (filter by company_id); use it rather than the approval-gated hudu_read / hudu_write / hudu_delete.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Exact asset id.
`name`	No	Exact or partial asset name.
`page`	No	Page number to fetch (1-based, default 1). This tool returns that one page and never follows it.
`slug`	No	Exact asset slug.
`search`	No	Free-text search within assets.
`archived`	No	true for archived assets, false for active ones.
`page_size`	No	Rows per page (1-100, default 25). The registry record caps a page at 100; a larger value is refused, never clamped.
`company_id`	No	Only assets belonging to this company id.
`updated_at`	No	ISO 8601; only assets updated at or after it.
`primary_serial`	No	Asset primary serial.
`asset_layout_id`	No	Only assets using this asset layout id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`rows`	Yes
`count`	Yes
`has_more`	Yes
`page_size`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial non-obvious behavior: it returns exactly one page and never pages through the tenant, pagination is vendor-side with later pages reached by raising page, the tool takes no operation argument, and it cannot be redirected to a write. It also notes page_size above the cap is refused rather than clamped.

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?

Front-loaded with the scope and bounding constraint, and every sentence carries information about pagination, filters, or routing. It is somewhat dense and longer than strictly necessary, but there is little filler.

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

Completeness5/5

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

An output schema exists, so return values need not be explained beyond the note that it returns at most page_size rows plus a more-exists flag. Combined with full parameter documentation, annotations, and explicit sibling routing, nothing needed to call it correctly is missing.

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 all 11 parameters are already documented in the schema. The description restates the filter set (company_id, primary_serial, asset_layout_id, search) without adding format or syntax meaning beyond it, so the baseline 3 applies.

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?

States a specific verb, resource, and scope: 'List ONE bounded page of assets across all companies'. It explicitly names the backing operation and distinguishes itself from siblings by naming hudu_get_asset_context and hudu_search as the tools for other needs.

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

Usage Guidelines5/5

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

Gives explicit routing: prefer hudu_get_asset_context to read one asset in full, hudu_search to find one by text, and use this ungated path rather than approval-gated hudu_read / hudu_write / hudu_delete. It also identifies the filter dimensions that select this tool (company_id, primary_serial, asset_layout_id, search).

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