iit-mcp-hudu

Get Article Context

hudu_get_article_context

Read-only

Fetch a Hudu article with its company and folder context in one call, so an agent starting from an article skips separate lookups.

Instructions

Fetch an article with its company and folder context. Preferred over three separate calls when an agent starts from an article. Returns ArticleContext. Bounded: every sub-list uses limit (default 25, max 100) — no sub-fetch walks the account. Not for paging: call hudu_search. Context depends on the resources available to this deployment; a refused credential answers UNAUTHORIZED (401, "Bad credentials") like every other tool, and any other failure keeps its real code — never partial results.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Numeric article id (hudu_get_article_context takes the id; use hudu_search or hudu_read / hudu_write / hudu_delete with articles.resolve to find it).
`opts`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Oct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses bounding behavior (every sub-list uses limit, default 25, max 100; no sub-fetch walks the account), the error contract (401 UNAUTHORIZED 'Bad credentials' for refused credentials, real codes otherwise), and the all-or-nothing guarantee ('never partial results'). These are exactly the operational traits annotations cannot convey.

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?

Tight, front-loaded, and every clause carries information (scope, preference, bounds, error behavior, exclusions). It is dense to the point of a slightly run-on error-semantics sentence, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-context tool with an output schema, the description covers scope, bounds, failure modes, and alternatives adequately; the output schema handles return values. The one gap is the referenced 'limit' that has no corresponding schema field, which could confuse an agent about how to control sub-list size.

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 only 50%, so the description must compensate, and it does add the per-sublist limit semantics (default 25, max 100) that appear nowhere in the schema. However, this 'limit' is not exposed in the input schema at all, leaving it ambiguous whether/how an agent can set it, which caps the score below 5.

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 ('Fetch an article with its company and folder context') and names the return type (ArticleContext). It explicitly distinguishes itself from sibling patterns by declaring itself preferred over 'three separate calls' and routing paging to hudu_search, so an agent can place it among hudu_list_articles / hudu_get_company_context without opening schemas.

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 when: 'when an agent starts from an article,' plus an explicit when-not: 'Not for paging: call hudu_search,' and names the alternative it replaces (three separate calls). This is prescriptive routing rather than implied context.

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