google-scholar-mcp

generate_bibtex

Generate a BibTeX citation entry for a publication from its title, authors, year, venue, and URL to use in LaTeX documents.

Instructions

Generate a BibTeX citation entry for a publication. Useful for creating properly formatted citations for LaTeX documents.

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

Input Schema

Name	Required	Description
`url`	No	Publication URL
`year`	No	Publication year
`title`	Yes	Publication title
`venue`	No	Journal or conference name
`authors`	Yes	List of author names

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 6, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects, authentication requirements, error handling, or how invalid inputs are treated. For a generation tool, this is a significant gap.

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

Conciseness5/5

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

The description is extremely concise with two sentences. The first sentence states the purpose and verb, and the second provides context. Every sentence earns its place with no wasted words.

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?

Given the lack of an output schema, the description should explain the return value, such as the format of the BibTeX string or citation key generation. It also does not mention if the tool supports all publication types (e.g., article, book). This leaves the agent uncertain about what to expect.

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 the baseline is 3. The description does not add any additional meaning to the parameters, such as the expected format for authors (e.g., 'First Last' vs 'Last, First') or handling of special characters. It merely restates the purpose.

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?

The description clearly states the action ('Generate a BibTeX citation entry') and the resource ('a publication'), with additional context about its use for LaTeX documents. It distinguishes itself from sibling tools like search_publications or get_citations, which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: the tool is useful for generating properly formatted citations for LaTeX documents. However, it lacks explicit guidance on when not to use it or alternatives, such as if the user needs citations in other formats.

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

Deploy Server