Skip to main content
Glama

edit

Insert, replace, delete, or move blocks within sections of a LaTeX document. Read and update raw LaTeX with lint checking. Control page breaks before or after sections.

Instructions

Manipulate document content structurally.

Actions:

  • insert: Add a new block at a position within a section.

  • replace: Replace a block at a position with new content.

  • delete: Remove a block at a position.

  • move: Move a block from one location to another.

  • read_raw: Read a RawLatex block with line numbers.

  • replace_raw: Update a RawLatex block (full or line-level) with lint check.

Sections are addressed by title path (e.g., 'Methods/Data Collection'). Blocks within a section are addressed by 0-based index.

page_break: For sections — "before", "after", "both", or "" to clear. Emits \clearpage before/after the section.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
block_typeNo
sectionNo
positionNo
contentNo
titleNo
levelNo
languageNo
pathNo
captionNo
headersNo
rowsNo
target_sectionNo
target_positionNo
templateNo
linesNo
lintNo
page_breakNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Minimal behavioral disclosure: mentions page_break emits \clearpage and lint check for replace_raw. Lacks details on side effects, error conditions, auth needs, or success/failure behavior. No annotations to supplement.

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

Conciseness3/5

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

Relatively concise with bulleted actions, but structure could be improved by front-loading key details and grouping parameter descriptions. Current format is acceptable but not optimal.

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 high complexity (18 params, no annotations, output schema exists but not described), the description is insufficient. It fails to explain many parameters, return values, or provide comprehensive usage context.

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?

With 0% schema description coverage and 18 parameters, the description only explains a few (action, section, position, page_break). Most parameters like content, title, level, headers, rows, etc. are not described, leaving significant gaps.

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 clearly states 'Manipulate document content structurally' and lists specific actions. The purpose is clear but does not explicitly differentiate from sibling tools like 'document', though the action list distinguishes it reasonably.

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., 'document' for reading). The description lists actions but does not explain contexts or situations where each action is appropriate.

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/aaronsb/texflow-mcp'

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