Skip to main content
Glama

Lint a file

lint_file
Read-onlyIdempotent

Validate text, Markdown, HTML, CSV/TSV, and locale files for AI tells, puffery, missing facts, and channel limits while preserving locale keys and placeholders.

Instructions

Lint a text, Markdown, HTML, CSV/TSV or locale file (json, po, arb, xliff, strings, strings.xml) inside an allowed folder. Locale keys and placeholders are never changed; CSV issues are keyed row/sku/column.

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": {
      "path": "<path>"
    },
    "name": "lint_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
mdNoTreat as Markdown; default comes from the extension
langNoauto detects the language per lineauto
pathYesFile inside an allowed folder; a relative path starts at the project folder
factsNoBrief or source text; English facts missing from it are flagged
formatNoWhalory format id; sets the limits for sentence length, emoji and exclamation marks
channelNoe.g. instagram.caption, linkedin.post (Pro data)
csv_keyNoCSV/TSV: id column used in issue keys
profileNoProfile name (whalory, starter-saas, en/saas), 'auto', or a path inside an allowed root
csv_columnsNoCSV/TSV: comma-separated text columns

Output Schema

NameRequiredDescriptionDefault
langYes
pathNo
statsYes
issuesYes
passedYes
summaryYes
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two genuinely useful behavioral facts beyond that: locale keys and placeholders are never altered, and CSV issues are keyed by row/sku/column. It says nothing about what the lint actually returns or how issues are grouped, though an output schema exists.

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?

Two compact sentences with the supported-format scope front-loaded and the two invariants trailing. Dense but no wasted clauses; the format list is long yet informative.

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?

With rich annotations, a fully described nine-parameter schema and an output schema, the description only needs to establish scope and guarantees, and it does. The one remaining gap is guidance on when to pick this over lint_text.

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 all nine parameters are already documented in the schema; the baseline of 3 applies. The description reinforces CSV keying behavior but adds no meaning beyond the schema for md, lang, facts, format, channel, profile or csv_columns.

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?

States a specific verb (lint) and an enumerated set of resources (text, Markdown, HTML, CSV/TSV, locale files) with a scoping constraint (inside an allowed folder). It does not explicitly contrast with the sibling lint_text, so an agent must infer the file-vs-text split from the path parameter alone.

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 when-to-use or when-not guidance, and no mention of the obvious alternative lint_text or check_final. The only implied routing signal is the required file path and the 'allowed folder' restriction, which the agent must reconstruct from the schema.

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