Skip to main content
Glama
BibTeX Reference Manager MCP

BibTeX Reference Manager MCP

Convert a bibliography

convert_bibliography
Read-only

Converts reference lists between BibTeX, RIS, CSL JSON, and styled plain text, detecting input format and cleaning page ranges, DOIs, and names.

Instructions

Convert a reference list between BibTeX, RIS, CSL JSON and plain text (a simple reference list style, APA by default, or MLA, IEEE, Chicago or Harvard when you pass style). The input format is detected unless you pass it. Page ranges, DOIs and names are cleaned on the way. Example: text is a BibTeX entry and to is "ris", and output is the same reference as RIS. Set from only to override detection.

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>",
      "to": "<to>"
    },
    "name": "convert_bibliography"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe format to write.
fromNoThe format of the text. Defaults to auto, which looks at the text to decide.
textYesThe reference list as text: BibTeX, RIS or CSL JSON.
styleNoThe citation style for the text output: apa, mla, ieee, chicago or harvard. Defaults to apa. Ignored for the other formats.

Output Schema

NameRequiredDescriptionDefault
toYesThe format that was written.
fromYesThe format that was read.
countYesHow many entries were converted.
outputYesThe converted reference list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / style
      Added value: +{
      +  "description": "The citation style for the text output: apa, mla, ieee, chicago or harvard. Defaults to apa. Ignored for the other formats.",
      +  "enum": [
      +    "apa",
      +    "mla",
      +    "ieee",
      +    "chicago",
      +    "harvard"
      +  ],
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.8/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 safety is covered; the description adds real value by disclosing that page ranges, DOIs and names are cleaned on the way, and that style is ignored for non-text targets. With an output schema present, it doesn't need to describe return values, but it could have said what a cleaned/converted failure looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the closing example ('text is a BibTeX entry and to is "ris"...') is awkward and low-value, and the final 'Set from only to override detection' repeats the schema's own wording on `from`.

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 simple pure-transform tool with full enum schema coverage, an output schema, and read-only annotations, the description covers formats, defaults, and side effects adequately. Nothing essential for a correct call is missing, though a note on input size or multi-entry lists would round it out.

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% and three of four parameters are enums, so the schema already carries the semantics; the description largely restates defaults (auto, APA) that are in the schema. The example and the 'set from only to override detection' note add only marginal meaning beyond it.

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 the specific verb (convert) and resource (reference list) and enumerates the four target formats, so the agent knows exactly what transformation happens. It is distinguishable from the sibling parse_bibliography because it names both source and destination formats rather than just reading input.

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?

It explains the option behavior (auto-detection of input, style defaults to APA, style ignored for non-text output), which is useful invocation guidance, but never says when to pick this tool over parse_bibliography or the other siblings. Usage is implied by the format list rather than stated.

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