Skip to main content
Glama

lint_latex

Lint a LaTeX snippet: report errors and return an auto-fixed version. Input code (the LaTeX source). Returns {errors, fixed_code, summary_en, summary_zh, elapsed_ms}.

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": {
      "code": "<code>"
    },
    "name": "lint_latex"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden, and it does disclose a key trait others would miss: the tool both analyzes and produces a fixed version. It also names the return fields including timing. It does not say whether the fix is a suggestion or authoritative, what classes of errors are detected, or whether there are input size or rate limits.

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?

Two sentences, front-loaded with the verb and resource, then parameter and return shape. Every clause carries information and there is no filler.

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?

For a one-parameter tool with no output schema, the description supplies the return field names, which is the main completeness risk covered. Remaining gaps are minor: input constraints and the nature of the auto-fix are not addressed.

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?

The single parameter has 0% schema description coverage, so the description must compensate; it does so only minimally by glossing 'code' as 'the LaTeX source'. That confirms the expected content but adds no detail on format, size, or whether a full document versus a fragment is accepted.

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 pairs a specific verb ('Lint') with a specific resource ('a LaTeX snippet') and immediately states both effects: reporting errors and returning an auto-fixed version. No sibling in the surrounding catalog performs LaTeX linting, so no disambiguation is required and none is missing.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this applies to LaTeX source text, but there is no explicit when-to-use, when-not-to-use, or mention of any alternative tool. Given the catalog has no comparable sibling, the omission is tolerable but leaves guidance at the minimum-viable level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.