iit-mcp-hudu

List Companies

hudu_list_companies

Read-only

List a single bounded page of company records with optional filters like name, city, or search. Returns up to page_size rows and indicates if more exist.

Instructions

List ONE bounded page of companies, backed by the fixed operation companies.list. Returns at most page_size rows plus whether more exist; it never pages through the tenant. This tool takes no operation argument and cannot be redirected to a write. Prefer hudu_search or hudu_resolve_any to identify a single company, and hudu_get_company_context to read one. This is the ungated path for the companies.list read; use it rather than the approval-gated hudu_read / hudu_write / hudu_delete.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Company city.
`name`	No	Exact or partial company name.
`page`	No	Page number to fetch (1-based, default 1). This tool returns that one page and never follows it.
`slug`	No	Exact company slug.
`state`	No	Company state.
`search`	No	Free-text search within companies.
`website`	No	Company website.
`id_number`	No	Company id number.
`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.
`updated_at`	No	ISO 8601; only companies updated at or after it.
`phone_number`	No	Company phone number.
`id_in_integration`	No	Vendor-side integration 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, but the description adds real behavioral context: returns at most page_size rows plus a 'more exist' flag, never pages through the tenant, takes no operation argument, cannot be redirected to a write, and is the ungated path versus approval-gated siblings. That is a substantive complement to the annotations.

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 pagination constraint before the routing advice; every sentence carries routing or behavioral information. It is slightly redundant, restating the no-paging constraint that the page/page_size field descriptions also cover.

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 an output schema present, return values need no elaboration, and the description still covers the mutation-non-redirectability, gating model, and sibling routing. An agent has everything needed to select and invoke this correctly.

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 the schema already documents all 12 parameters with types, defaults, and bounds. The description reinforces the page/page_size semantics (one page, cap refusal) but adds no filter syntax or values beyond what the schema states, 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 and resource with scope: 'List ONE bounded page of companies, backed by the fixed operation companies.list', and explicitly frames it as a single-page, non-paginating read. This lets an agent distinguish it from hudu_search, hudu_resolve_any, and hudu_get_company_context without opening any schema.

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?

Names alternatives and the conditions that select them: 'Prefer hudu_search or hudu_resolve_any to identify a single company, and hudu_get_company_context to read one.' It also routes the agent away from the approval-gated hudu_read / hudu_write / hudu_delete, which is an explicit when-not.

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