Skip to main content
Glama

insert_caption

Insert a caption paragraph after a specified paragraph in a Word document, with customizable label (e.g., Figure or Table).

Instructions

Insert a caption paragraph after the specified paragraph.

Args: after_para_id: paraId of the paragraph to insert after. text: Caption description text (without label/number prefix). label: Caption label, e.g. "Figure" or "Table" (default "Figure").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
after_para_idYes
textYes
labelNoFigure

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries the burden but only states it inserts a caption. It does not disclose side effects like auto-numbering, updates to caption lists, or dependencies on document state. Minimal behavioral info beyond the name.

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 very brief, uses a clear Args structure, and every sentence adds value. No redundancy or fluff.

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?

The description explains the action and all parameters sufficiently. It does not mention return value or error conditions, but the output schema likely covers that. It could hint at interaction with caption numbering or lists, but overall is complete for a straightforward insertion tool.

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

Parameters5/5

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

The description provides clear, value-added explanations for all three parameters with zero schema coverage. It clarifies the role of after_para_id, text (without prefix), and label with examples and default.

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 it inserts a caption paragraph after a specified paragraph, using verb+resource+location. It distinguishes from siblings like insert_paragraph and add_cross_reference by specifying it's for captions with label and text.

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 on when to use this tool versus alternatives (e.g., insert_paragraph or add_cross_reference). No prerequisites or context provided beyond the action itself.

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/SecurityRonin/docx-mcp'

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