Skip to main content
Glama
Sign In
huly-mcp-selfhost

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_document

Creates an empty Huly document in a selected teamspace, optionally under a parent document, and returns its ID so you can add content in a separate update step.

Instructions

Create an empty document in a teamspace, optionally under a parent; returns its id. Write the body with update_document

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "teamspaceId": "<teamspaceId>",
      "title": "<title>"
    },
    "name": "create_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesDocument title
parentIdNoParent document id; omit for top-level
workspaceYes
teamspaceIdYesTeamspace id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.6.2
    • addedInput schema / properties / title / description
      Added value: +"Document title"
  2. First observedv3.5.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false and a title, so the description must carry behavior and does contribute two useful facts: the created document is empty and the call returns its id, implying a create-then-update workflow. It says nothing about permission requirements, teamspace scoping effects, title uniqueness/collisions, or failure modes, which are the remaining risks for a mutation.

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?

Two short sentences, front-loaded with the action and scope, with the return value and follow-up instruction packed efficiently. No filler; a slightly clearer separation of the follow-up hint would make it ideal.

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 four-parameter creation tool with no output schema, the description covers the essential contract: what is created, where, the optional parent relationship, and the returned id. Missing permission/error context is minor given the annotations cover the non-destructive profile.

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 coverage is 75%, so the schema already documents title, parentId, and teamspaceId. The description reinforces the teamspace and optional-parent semantics but adds no format, ownership, or placement detail beyond the schema, and the undocumented 'workspace' parameter is not clarified anywhere.

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 ('Create an empty document'), scopes it ('in a teamspace, optionally under a parent'), and disambiguates the resulting artifact ('empty document') from a document with content. An agent knows exactly what will exist after the call and can distinguish it from update_document 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 Guidelines4/5

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

Explicitly routes content authoring to a named sibling ('Write the body with update_document'), which is the key decision an agent faces after creation. It stops short of stating exclusion conditions (e.g., when to prefer an existing document or a different creation path), so it is clear context rather than a full when/when-not rule.

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