Skip to main content
Glama
Sign In
claucloverleaf

claucloverleaf

by SolthaX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

overleaf_insert_lines

Insert new lines into an Overleaf project document before a specified line or append them at the end, with optional tracked-change suggestions.

Instructions

Insert new line(s) into a document, before a given line or at the end.

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": {
      "project": "<project>",
      "path": "<path>",
      "text": "<text>"
    },
    "name": "overleaf_insert_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath in the project, e.g. 'main.tex' or 'chapters/intro.tex'.
textYesLine(s) to insert.
projectYesProject id, Overleaf project URL, or exact project name.
before_lineNoInsert before this 1-based line; omit to append at the end.
track_changesNoSubmit as a tracked change (suggestion) instead of a direct edit.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so mutation semantics are partly covered. The description adds nothing beyond that: it does not say whether inserting shifts subsequent line numbers, whether multiple insertions are atomic, or what happens with track_changes enabled versus a direct edit.

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?

One short sentence, front-loaded with the core action and no redundancy. It is efficient, though brevity comes at the cost of missing routing information.

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

Completeness3/5

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

An output schema exists and annotations cover the safety profile, so the description needn't explain return values. Still, for a mutation tool in a crowded sibling set, the description omits how it differs from write/replace tools and the consequence of inserting lines on existing line references.

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 description coverage is 100%, so baseline is 3. The description restates the before_line/append-at-end behavior already documented in the schema and adds no extra detail on formatting of 'text', newline handling, or line-number validity.

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 names a specific verb and resource ('Insert new line(s) into a document') and clarifies placement semantics (before a given line or at the end). It does not differentiate from close siblings such as overleaf_replace_lines or overleaf_write_file, which overlap heavily, so it stops short of a 5.

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?

There is no when-to-use guidance and no mention of alternatives among 19 siblings, several of which (overleaf_write_file, overleaf_replace_lines, overleaf_replace_text) could plausibly do the same job. The clause about position is a parameter behavior, not a selection criterion.

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