Skip to main content
Glama
Sign In
HWP MCP Server

HWP MCP Server

by mjyoo2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_bullet_style

Apply bullet style to the current paragraph in an HWP document, specifying bullet type, character, or size as needed.

Instructions

Apply bullet style to current paragraph.

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": {
      "doc_id": "<doc_id>"
    },
    "name": "set_bullet_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
doc_idYes
characterNo
bullet_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states the action and target, but does not reveal whether existing bullets are replaced, whether a document must be open, or what happens when the selection spans multiple paragraphs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, compact sentence with no filler. The action and target are front-loaded, making it easy to parse quickly.

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?

For a mutating tool with four parameters, no annotations, and zero schema descriptions, the one-line description leaves significant gaps. The presence of an output schema does not compensate for missing parameter semantics, usage conditions, or behavioral side effects.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no explanation of the parameters (size, character, bullet_type). The agent cannot infer valid values, optionality semantics, or how the parameters combine to produce a bullet style.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('apply') on a specific resource ('bullet style') with a clear target ('current paragraph'). It is understandable but does not explicitly differentiate itself from sibling tools like set_numbering_style or set_paragraph_style.

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 guidance is given on when to use this tool versus alternatives, nor are prerequisites like cursor position or selection state mentioned. The intended usage is only implied by the phrase 'current paragraph'.

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