Skip to main content
Glama

List Assets

hudu_list_assets
Read-onlyIdempotent

List assets across Hudu companies, filtering by search, company, or asset layout. Retrieve documented IT items and their custom fields for read-only use.

Instructions

List assets in Hudu. An asset is any documented thing that belongs to a company — a server, a workstation, a firewall, a licence, a contact. The asset layout it was created from decides which custom fields it carries.

This is the only route that reads assets across every company, and it is read-only: creating, updating, archiving and deleting an asset all happen under /companies/{company_id}/assets. Keep the company_id of any record you might write to — hudu_get_asset, hudu_create_asset, hudu_update_asset, hudu_archive_asset and hudu_delete_asset all require it, and it cannot be recovered from the asset id alone. If you narrow the response with fields, keep "company_id" in the list.

Custom field values come back under fields as {id, label, value, position} objects rather than as top-level keys. search is the right first filter for a hostname or a fragment of a name; id is how you turn a bare asset id into the company id needed to write to it.

Returns an object with items plus pagination facts. Note that the Hudu API returns no total count for any collection, so page_was_full is the only honest signal that more records exist — read pagination_note before concluding a list is complete.

Operation class: Read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoReturn the single asset with this id. Useful when you hold an asset id and need its `company_id` before you can write to it.
nameNoMatch against the asset name.
pageNo1-based page number. Hudu has no cursor or offset — only pages.
slugNoURL slug, if you already know it.
fieldsNoReturn only these top-level fields on each record. Use it to keep large lists small — e.g. ["id","name","company_id"]. Unknown field names are ignored.
searchNoBroad text search across asset fields. The best first filter for a name.
archivedNotrue returns archived assets instead of active ones.
page_sizeNoRecords per page (1-100, default 25). Hudu publishes no maximum, so this client clamps at 100; larger values are rejected here rather than silently altered by the server.
company_idNoReturn only assets owned by this company.
updated_atNoISO-8601 range as "start,end". Either side may be omitted — "2026-01-01T00:00:00Z," means everything changed since that moment.
primary_serialNoMatch against the serial number.
asset_layout_idNoReturn only assets built on this asset layout, e.g. only servers.
response_formatNoOutput shape. 'json' (default) is compact and machine-readable; 'markdown' is easier for a person to read but larger.json
Behavior5/5

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

The description goes well beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint) by disclosing that the API returns no total count, so page_was_full is the only honest signal for more records, and 'pagination_note' should be read. It also reveals the shape of custom fields under 'fields' and explains response_format behavior, adding genuine behavioral context.

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?

The description is longer than average but every paragraph earns its place: the first defines assets, the second covers scope and relationship to write endpoints, the third explains custom fields and filtering strategy, and the last covers return shape and pagination quirks. It is well-structured and front-loaded, though slightly verbose in places.

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?

For a tool with 13 parameters, no output schema, and no documented total count, this description is exceptionally complete. It explains the return shape ('object with items plus pagination facts'), how to handle pagination honestly, how to use fields and search, and the relationship to write operations. Nothing essential is left unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description enriches nearly every parameter with practical guidance: fields 'use it to keep large lists small', page_size explains the client clamps at 100 and rejects larger values, updated_at explains the ISO-8601 range format with examples, and id explains its role in recovering company_id. This adds meaning beyond the schema definitions.

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 uses a specific verb ('List assets in Hudu'), defines what an asset is, and distinguishes this tool from siblings by stating it is 'the only route that reads assets across every company.' This clearly differentiates it from hudu_list_company_assets and other asset-related tools.

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?

The description explicitly states when to use this tool versus others, including that it is the only cross-company read route, that write operations live under /companies/{company_id}/assets, and that 'search' is the best first filter. It also warns to keep company_id because it cannot be recovered from asset id, and mentions hudu_get_asset as an alternative for getting a single asset.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZenixSolutions/hudu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server