Skip to main content
Glama
BibTeX Reference Manager MCP

BibTeX Reference Manager MCP

Lint entries

lint_entries
Read-only

Check a reference list for problems: missing required fields for the entry type, bad page ranges, titles that are not capitalized, invalid DOIs, odd years, repeated keys and unescaped &, %, _ or # in titles, journal names and other text…

Instructions

Check a reference list for problems: missing required fields for the entry type, bad page ranges, titles that are not capitalized, invalid DOIs, odd years, repeated keys and unescaped &, %, _ or # in titles, journal names and other text fields (rule unescaped-character). Each issue names the entry key, the field and a plain message. Example: an @article with no journal field gives an issue with the rule missing-field and the field journal. Pass the whole list as text so repeated keys can be found.

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": {
      "text": "<text>"
    },
    "name": "lint_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe reference list as text: BibTeX, RIS or CSL JSON.
formatNoThe format of the text. Defaults to auto, which looks at the text to decide.

Output Schema

NameRequiredDescriptionDefault
countYesHow many entries were checked.
errorsYes
issuesYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedOutput schema / properties / issues / items / properties / rule / enum
      Previous value: -[
      -  "missing-field",
      -  "bad-pages",
      -  "uncapitalized-title",
      -  "invalid-doi",
      -  "bad-year",
      -  "duplicate-key"
      -]New value: +[
      +  "missing-field",
      +  "bad-pages",
      +  "uncapitalized-title",
      +  "invalid-doi",
      +  "bad-year",
      +  "duplicate-key",
      +  "unescaped-character"
      +]
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known; the description adds valuable behavioral detail by naming the rule set, explaining that each issue carries entry key, field and message, and giving a concrete @article/missing-field example. It does not explicitly affirm that nothing is written back to any file, which would be the last useful addition for a read-only checker.

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?

Front-loaded with the purpose, then the rule inventory, then the issue shape and an example — a sensible ordering with little waste. The rule list and the worked example overlap slightly (both explain issue fields), but every sentence carries information.

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

Completeness5/5

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

For a read-only lint tool with an output schema and fully documented parameters, the description covers what is checked, the accepted input formats, the whole-list requirement, and the shape of an issue. Nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but 'Pass the whole list as text so repeated keys can be found' adds genuine semantics: the text parameter must hold the entire list, not an excerpt or single entry. That constraint is not derivable from the schema's minLength: 1 alone.

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 and resource ('Check a reference list for problems') and enumerates exactly which problems are detected, so the agent knows precisely what the tool does. It does not explicitly distinguish itself from siblings like fix_entries or dedupe_entries, leaving the agent to infer that this tool only reports and never repairs.

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?

The final sentence gives real usage guidance ('Pass the whole list as text so repeated keys can be found'), which tells the agent how to call it correctly. However, there is no explicit when-to-use/when-not guidance relative to fix_entries (report vs. repair) or dedupe_entries, so routing must be inferred.

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