Skip to main content
Glama
Sign In
Hangeul-mcp

Hangeul-mcp

by pblsketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_document_from_spec

Generate a HWPX document from a DocumentSpec v1 payload, preserving original formatting while applying AI-generated values.

Instructions

Create an HWPX from a DocumentSpec v1 payload (validated template union; delegate).

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": {
      "spec": "<spec>",
      "out_path": "<out_path>"
    },
    "name": "create_document_from_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
out_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a mutation ('Create') but lacks details on validation, side effects, permissions, or response behavior. The reference to 'validated template union' is vague.

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 very concise at one sentence. It front-loads the primary purpose. However, it could be slightly more structured or include key behavioral hints without adding verbosity.

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

Completeness2/5

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

Given the high number of sibling tools and the presence of nested objects in the schema, the description is incomplete. It fails to explain the 'DocumentSpec v1' structure or how this tool differs from other document creation tools, leaving significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% with no descriptions in the schema. The tool description adds minimal context: 'DocumentSpec v1 payload' for spec and 'out_path' is self-explanatory, but spec structure and constraints remain unclear. For a complex object parameter, more detail is needed.

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 action 'Create an HWPX', specifies the source 'DocumentSpec v1 payload', and distinguishes from sibling creation tools by mentioning 'validated template union; delegate', which implies a specific input format.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like create_document_from_blocks or create_hwpx_from_markdown. The phrase 'delegate' hints at internal usage, but no when-to-use or when-not-to-use instructions.

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