Skip to main content
Glama

Create Relation

hudu_create_relation

Link any two Hudu records—asset, password, company, article—by creating a from/to relation. Returns the new relation and flags invalid inputs.

Instructions

Create a new relation in Hudu. A relation is a link between any two Hudu records — an asset to the password that opens it, an article to the company it documents — stored as a from/to pair of type-and-id. Hudu exposes no update route for relations, so changing one means deleting it and creating a replacement.

Returns the created record, including the id Hudu assigned. Hudu answers 422 with the offending field named when validation fails.

Operation class: Create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toable_idYesNumeric Hudu id of the destination record, of the type named in `toable_type`.
is_inverseNoLeave this unset. Hudu creates the reverse link automatically and sets this flag on the copy it generates; sending true yourself declares the relation you are creating to be that generated mirror.
descriptionNoFree text explaining what the link means, shown alongside it on both records — "admin credentials for this firewall". Worth filling in: the record names alone rarely say why two things were linked.
fromable_idYesNumeric Hudu id of the origin record, of the type named in `fromable_type`.
toable_typeYesKind of record at the destination of the link. Hudu documents six: Asset, Website, Procedure, AssetPassword (a stored password record), Company and Article. The string is case-sensitive and is Hudu's internal class name, not the label shown in the UI — a password is "AssetPassword", not "Password".
fromable_typeYesKind of record at the origin of the link. Hudu documents six: Asset, Website, Procedure, AssetPassword (a stored password record), Company and Article. The string is case-sensitive and is Hudu's internal class name, not the label shown in the UI — a password is "AssetPassword", not "Password".
Behavior5/5

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

The description goes beyond annotations by disclosing that there is no update route, that the response includes the created record with the assigned id, and that validation failures return a 422 with the offending field. These are valuable behavioral details not present in 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?

The description is well-structured and information-dense, but the final 'Operation class: Create' sentence is redundant with the title and could be trimmed. Overall, each sentence contributes to understanding.

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?

Given that there is no output schema, the description adequately covers the return value (created record with id) and error behavior (422). It also explains the tool's position in Hudu's relation lifecycle, making it complete for a create operation.

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. The description adds extra meaning for is_inverse (warning against manual use), explains the case-sensitive internal class names for type parameters, and encourages filling the description field. This exceeds baseline.

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?

The description clearly states the tool creates a relation in Hudu and defines what a relation is with concrete examples. It uses a specific verb and resource, and distinguishes it from siblings like hudu_list_relations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the tool's role and notably mentions that Hudu has no update route for relations, implying the delete-and-recreate pattern. However, it does not explicitly state when to prefer this over alternative tools or mention any prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZenixSolutions/hudu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server