Skip to main content
Glama

List Assets for a Company

hudu_list_company_assets
Read-onlyIdempotent

List company-owned assets such as servers, workstations, firewalls, licences, and contacts. Supports pagination and archived flag to retrieve active or archived records.

Instructions

List the assets belonging to one company. 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 route accepts paging and the archived flag and nothing else. To filter by name, serial, layout or free text within a company, call hudu_list_assets with company_id set instead — it reaches the same records and supports the full filter set.

Returns an object with items plus pagination facts. Hudu returns no total count for any collection, so page_was_full is the only honest signal that more records exist.

Operation class: Read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number. Hudu has no cursor or offset — only pages.
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.
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_idYesNumeric id of the company that owns this asset. Not optional and not guessable — an asset id belonging to company A returns 404 under company B, indistinguishable from a deleted asset.
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?

Annotations already declare readOnly/idempotent/destructive hints, and the description adds valuable behavioral context beyond those: pagination lacks a total count, page_was_full is the only reliable signal for more records, and company_id scoping causes 404 for mismatched owners. This extra disclosure (e.g., 404 ambiguity, no total count) meaningfully enriches the agent's understanding.

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 organized into three clear paragraphs: definition, scope/alternative, and return/pagination. Each paragraph earns its place, but it is slightly longer than the minimum needed. The 'Operation class: Read' footer is redundant given annotations, but not harmful.

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?

With no output schema, the description appropriately explains the return shape ('items' plus pagination facts, page_was_full signal) and the influence of asset layout on custom fields. It covers the key nuances needed to use the tool correctly, including limitations and alternatives, making it complete for a list operation with this complexity.

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

Parameters4/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 baseline is 3. The description adds value by clarifying that only paging and archived are accepted—meaning no filtering—and by directing users to hudu_list_assets for filter support. This helps an agent decide whether this tool's parameter set meets the need, though it doesn't detail syntax beyond the schema.

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 opens with a specific verb+resource: 'List the assets belonging to one company.' It also defines what an asset is, which disambiguates from other resources. It distinguishes itself from the sibling hudu_list_assets by noting this route accepts only paging and archived, while hudu_list_assets supports full filtering.

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?

Explicit when-to-use guidance is provided: 'To filter by name, serial, layout or free text within a company, call hudu_list_assets with company_id set instead — it reaches the same records and supports the full filter set.' It also states what the route accepts ('paging and the archived flag and nothing else'), making the scope clear.

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