Skip to main content
Glama
BibTeX Reference Manager MCP

BibTeX Reference Manager MCP

Generate cite keys

generate_cite_keys
Read-only

Generate consistent citation keys from first author, year, and title word for BibTeX, RIS, or CSL JSON lists; duplicate keys get letter suffixes.

Instructions

Create consistent cite keys from the first author's family name, the year and the first meaningful word of the title, like smith2024deep. Repeated keys get a letter added. Returns the old and new key for each entry and the list as BibTeX with the new keys. Example: an entry with key old1, author "Smith, John", year 2024 and title "Deep Learning for Graphs" gives old_key old1 and new_key smith2024deep, or smith2024 when include_title_word is false.

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": "generate_cite_keys"
  }
}

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.
show_bibtexNoAlso print the full entries with the new keys in the text reply, ready to paste into a .bib file. Defaults to false.
include_title_wordNoAdd the first meaningful title word, so you get smith2024deep and not smith2024. Defaults to true.

Output Schema

NameRequiredDescriptionDefault
keysYes
countYes
bibtexYesThe list as BibTeX using the new keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / show_bibtex
      Added value: +{
      +  "description": "Also print the full entries with the new keys in the text reply, ready to paste into a .bib file. Defaults to false.",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A4.2/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 description's job is lighter. It still adds real behavioral context: duplicate keys get a suffixed letter, and the tool returns both old and new keys plus a BibTeX rendering, which an agent could not infer from the annotations.

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 key-generation rule, then duplicate handling, then return shape, then an example. Efficient overall, though the closing example partly repeats the schema's own wording for include_title_word and could be tightened.

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?

Output schema exists, yet the description still explains what comes back (old/new key pairs and BibTeX), and it covers the naming algorithm, collision handling, and the toggle behavior. Nothing an agent needs to invoke this 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. The description goes slightly beyond by showing the concrete effect of include_title_word=false (smith2024 vs smith2024deep) and by tying show_bibtex to the returned BibTeX list, giving the parameters operational meaning rather than restating them.

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?

States a specific verb+resource (create cite keys) and pins down the exact algorithm: first author family name, year, first meaningful title word, with a concrete example (smith2024deep). This is clearly distinguishable from siblings like convert_bibliography or dedupe_entries.

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 description implies when the tool is useful (you want consistent keys) but never states explicit when-to-use conditions, prerequisites, or why to choose it over fix_entries or dedupe_entries. Usage is inferable from purpose alone, which is the definition of implied guidance.

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