Skip to main content
Glama

BibTeX book entry

bpj_bibtex_book_entry
Read-onlyIdempotent

Generate a BibTeX book entry from a citation key, structured names, year and publisher.

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": {
      "title": "<title>",
      "authors": "<authors>",
      "year": "<year>",
      "key": "<key>",
      "publisher": "<publisher>"
    },
    "name": "bpj_bibtex_book_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
yearYes
titleYes
authorsYes
publisherYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and repeatability profile is fully covered by structured data. The description adds only the nature of the emitted artifact (a BibTeX book entry), saying nothing about escaping, key-collision behavior, field ordering, or what happens when a required field is invalid. With annotations carrying the safety burden, this is adequate but thin.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of detail rather than from tight editing of richer content.

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

Completeness2/5

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

For a five-required-parameter generator with no output schema and zero schema description coverage, the description is too sparse: it neither specifies the input string formats nor indicates which BibTeX fields the generated entry will contain. An agent could call it, but only by guessing at author formatting and key conventions.

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

Parameters2/5

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

Schema description coverage is 0% and all five parameters are required, so the description must compensate and largely does not. It references the citation key, 'structured names', year and publisher, but explains no formats: the author line-per-name convention, key character rules, the 1-9999 year bounds, and the title parameter (not mentioned at all) are left undocumented.

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+resource pair ('Generate a BibTeX book entry') and names the four categories of input it consumes, so an agent knows immediately what artifact comes out. It does not differentiate against any sibling, but the siblings listed are unrelated utilities rather than near-duplicates, so the cost is low.

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?

There is no when-to-use guidance, no preconditions, and no mention of alternatives or of what to do for non-book citation types (article, inproceedings). The agent must infer that this tool is only appropriate for books with a publisher.

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.