iit-mcp-hudu

Discover Operations (Catalog)

hudu_list_operations

Read-only

Discover Hudu SDK operations, their exposing tools, effects, arguments, and confirmation needs. Filter or page the catalog to find capabilities reachable only via hudu_read/hudu_write/hudu_delete.

Instructions

List the operations the Hudu SDK implements, with the tool that exposes each one (when it has one), its effect, whether it needs a dry run or a confirmation flag, and the arguments it requires. The tool list on this server is a SUBSET: this is a curated core profile, and the catalog is how you discover a capability that has no tool of its own — find the row, call hudu_describe_operation for the exact schema, then hudu_read/hudu_write/hudu_delete. Rows with no "tool" are reachable only through hudu_read/hudu_write/hudu_delete. Rows with "reachable": false are deliberately not callable here and state why (an unbounded read, or a binary/download surface). Bounded: limit defaults to 40 and is hard-capped at 100, offset pages through the rest; the whole catalog is ~10k tokens, so ask for a filter or a page rather than dumping it.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Rows per page (1-100, default 40); the whole catalog is ~10k tokens, so page it.
`effect`	No	Only rows with this effect.
`offset`	No	Row offset, for paging.
`resource`	No	Only rows of this registry resource (e.g. "assets").
`unexposed_only`	No	Only rows with NO tool of their own — the capabilities reachable only through hudu_read / hudu_write / hudu_delete.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	Yes
`limit`	Yes
`offset`	Yes
`matched`	Yes
`has_more`	Yes
`total_operations`	Yes
`reachable_operations`	Yes
`unexposed_operations`	Yes
`unreachable_operations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Oct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint; the description adds substantial behavioral context: why certain rows are deliberately uncallable (unbounded reads, binary/download surfaces), the reachability rules, and the hard cap of 100 with a ~10k-token catalog cost. This is exactly the extra context annotations cannot express.

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 purpose, then the workflow, then the edge cases and paging constraints; each sentence carries information. It is dense and slightly run-on, but no sentence is filler, so it stays efficient rather than padded.

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. Given that, the description covers everything an agent needs: what the catalog contains, how to act on a row, which rows are unreachable and why, and the paging/token budget.

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 description coverage is 100%, so the schema already documents limit, offset, effect, resource, and unexposed_only, making 3 the baseline. The description goes further by explaining the operational rationale behind paging (hard-capped at 100, whole catalog ~10k tokens) and why to prefer a filter or a page over a full dump.

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 ('List the operations the Hudu SDK implements') and immediately narrows the payload to the tool mapping, effect, dry-run/confirmation needs, and required arguments. It also positions itself against siblings by calling out that the tool list is a curated subset and that this catalog covers capabilities with no tool of their own.

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 an explicit discovery workflow: find the row, call hudu_describe_operation for the exact schema, then hudu_read/hudu_write/hudu_delete. It names the conditions that select alternatives (rows with no 'tool' are reachable only via the generic verbs; 'reachable: false' rows are not callable) and even advises filtering/paging instead of dumping.

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