Skip to main content
Glama
msoukhomlinov

iit-mcp-hudu

by msoukhomlinov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search Hudu (search | help | resources)

hudu_search
Read-only

Search articles, assets, companies, users, groups, websites, and password records; return ranked fuzzy matches with snippets, scores, and fetch calls for full records.

Instructions

Search Hudu. One tool, three modes: mode="search" (the default) runs the query; mode="help" returns how to use this tool; mode="resources" returns what is searchable and what each vendor text filter really covers. Only "search" needs query. mode="search": ranked, fuzzy search over article TITLE and BODY content, asset names, custom-field VALUES and identifiers, plus company/user/group/website names. Each hit carries resource, id, a snippet, a 0-100 score band and the fetch call for the full record. As a TOOL it defaults to tier "index" (build or await the body index), so the answer is complete rather than body-blind. Honesty: limit default 8 / max 25, snippetChars default 200 / max 400 (0 = none); a bound that bites sets meta.complete false and names itself in meta.reasons. hits=[] is a complete "nothing matched" answer ONLY when meta.complete is true and meta.degraded is null - read degraded first: it says when bodies were not searched ("body-not-indexed") or the index was cold ("vendor-only"). Not for identity lookup (hudu_find_* / hudu_get_*) or for paging (hudu_list_*). A field the mode cannot honour is a CONFIG_ERROR naming the fields it honours; a missing query is a CONFIG_ERROR naming mode:"help", never a silent help fallback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoWhich mode to run. Default "search" (the query runs; nothing else is needed). "help" returns how to use this tool. "resources" returns what is searchable. A field the selected mode cannot honour is a CONFIG_ERROR naming the fields it does honour - never silently ignored.search
tierNomode="search" only. THIS TOOL DEFAULTS TO "index" (build or await the body index, so the answer is complete rather than body-blind). "auto" is the SDK default for programmatic callers; "vendor" answers from Hudu search alone.
limitNomode="search" only. Ranked hits: 1-25, default 8. A larger value is a CONFIG_ERROR, never clamped.
queryNomode="search" only, and REQUIRED there: omitting it is a CONFIG_ERROR naming mode:"help" (it never falls back to help). Partial words are tolerated; article BODY content is searched. Hudu's own search differs by resource. Companies, websites, passwords and assets match the words in order with gaps allowed, so reordering words can miss a record ("acme corp" finds "Acme Corp Pty", "corp acme" may not). Users, groups and password folders match the whole query as one exact phrase, so use one word. Some instances answer from a fuzzy index that returns records matching only some of the words. Indexed articles and assets score each word independently (match.coverage). On a multi-word query, when the full phrase finds nothing, the tool retries the individual words and ranks partial matches lower; match.coverage shows how good a match is. For an exact lookup, search one distinctive word.
topicNomode="help" only. Which help section to return (default "core"; "all" adds query syntax and scoring). Rejected in the other modes.
refreshNomode="search" only. true forces a body-index rebuild before answering.
min_scoreNomode="search" only. 0-100 score floor: hits below the floor are left out of the result, and NO count of them is reported - an empty result can be the floor, not absence. meta.scanned (candidates scored before the floor) and meta.returned separate absence from exclusion: scanned 0 = nothing scored at all; scanned > 0 with returned 0 = candidates scored but none returned - below the floor, or excluded by the company_id, updated_since or scope filters (lower or drop min_score, or relax those filters, to see what was left out).
resourcesNomode="search" only. Which resources to search; default ["articles","assets"]. The resources this deployment's credential may read (HUDU_SEARCH_RESOURCES), from the SDK's searchable set: articles, asset_passwords, assets, companies, groups, password_folders, users, websites.
company_idNomode="search" only. Scope the scan to one company.
exact_onlyNomode="search" only. true disables fuzzy matching, still ranked and snippeted. Default false.
snippetCharsNomode="search" only. Snippet characters per hit: 0-400, default 200, 0 = no snippet.
updated_sinceNomode="search" only. ISO 8601; only records updated at or after it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply readOnlyHint and openWorldHint; the description carries far more: the tool defaults to tier "index" (building/awaiting a body index), meta.complete/meta.degraded semantics ('body-not-indexed', 'vendor-only'), the rule that hits=[] is only a real null result when meta.complete is true and meta.degraded is null, and that out-of-range limits are CONFIG_ERRORs rather than clamped. That is substantial behavioral disclosure beyond structured fields.

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 three modes and their trigger conditions, then the search semantics, then the honesty/limits paragraph. Nearly every sentence carries operational weight, though the density is high and the honesty paragraph could be tightened without losing meaning.

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?

For a 12-parameter, 3-mode search tool this is complete: it covers mode selection, query syntax per resource, degradation states, empty-result interpretation, filter-vs-absence distinction, and error behavior. An output schema exists, so return-value documentation is not required, yet the meta-field semantics are explained anyway.

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%, so the baseline is 3, but the description genuinely adds meaning: it flags that the tool's tier default ("index") differs from the SDK default ("auto"), and it explains min_score's silent exclusion with meta.scanned vs meta.returned as the way to distinguish absence from filtering. The query parameter's per-resource matching rules are also spelled out. It stops short of 5 only because most enum/bound syntax is already in 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?

States a specific verb (ranked, fuzzy search) and precisely enumerates the searched surfaces: article TITLE and BODY, asset names, custom-field VALUES and identifiers, plus company/user/group/website names. It also explicitly excludes sibling territory ('Not for identity lookup (hudu_find_* / hudu_get_*) or for paging (hudu_list_*)'), so an agent can distinguish it from every adjacent tool 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?

Names alternatives and the conditions that select them: hudu_find_*/hudu_get_* for identity lookup, hudu_list_* for paging, and mode="help"/"resources" for self-description. It further guides query construction ('For an exact lookup, search one distinctive word') and explains the retry-on-partial behavior, which is real when-to-use guidance.

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

Deploy Server

Other Tools