iit-mcp-hudu

List Articles

hudu_list_articles

Read-only

List one page of knowledge-base articles using filters like name, slug, or search, returning up to page_size rows and whether more exist. This ungated read avoids approval-gated operations.

Instructions

List ONE bounded page of knowledge-base articles, backed by the fixed operation articles.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 to find an article by text, and hudu_get_article_context to read one. This is the ungated path for the articles.list read; use it rather than the approval-gated hudu_read / hudu_write / hudu_delete.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Exact or partial article name.
`page`	No	Page number to fetch (1-based, default 1). This tool returns that one page and never follows it.
`slug`	No	Exact article slug.
`draft`	No	true for drafts, false for published articles.
`search`	No	Free-text search within articles.
`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 articles belonging to this company id.
`updated_at`	No	ISO 8601; only articles updated at or after it.
`enable_sharing`	No	Only articles with sharing enabled/disabled.

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?

Beyond the readOnlyHint annotation, it discloses that it returns at most page_size rows plus a has-more flag, never auto-pages the tenant, accepts no operation argument, and cannot be redirected to a write. It also flags the gated/ungated distinction relative to hudu_read/hudu_write/hudu_delete, which is real operational 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?

Front-loads the core behavior (bounded page, fixed operation) before routing advice, and each sentence carries actionable content. It is somewhat dense across five sentences, but nothing is pure 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?

With an output schema present and annotations covering the safety profile, the description only needs to cover scope, paging semantics, and routing – all of which it does. Nothing an agent needs to invoke 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 9 parameters are already documented in the schema. The description echoes page_size behavior ('returns at most page_size rows') but adds no syntax or format detail beyond the schema. 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?

States a specific verb (List) and resource (knowledge-base articles) with explicit scope: one bounded page backed by the fixed operation articles.list. It also names the siblings it is not (hudu_search, hudu_get_article_context), so an agent can distinguish it without opening a 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?

Gives explicit routing: prefer hudu_search for text lookup, hudu_get_article_context to read a single article, and use this tool rather than the approval-gated hudu_read/hudu_write/hudu_delete. Both when-to-use and when-to-use-something-else are stated plainly.

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