bibtex-mcp

Google Scholar BibTeX

google_scholar_bibtex

Search Google Scholar for a paper title and retrieve multiple BibTeX citations, ranked to prefer archival conference or journal records over preprints.

Instructions

Search Google Scholar for a paper title and return multiple BibTeX options from Scholar's citation export flow, ranked to prefer archival conference/journal records over preprints. Does not bypass CAPTCHA or access controls.

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": {
      "query": "<query>"
    },
    "name": "google_scholar_bibtex"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Paper title or Scholar search query.
`exactTitle`	No	Prefer exact title matches before archival ranking.
`maxResults`	No	Number of Scholar options to return.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Without annotations, the description carries full burden. It discloses the ranking logic and the limitation about CAPTCHA/access controls, but could mention side effects (none) or rate limits. Still, it provides substantial behavioral context.

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?

Two concise sentences, front-loaded with main function and ranking, then limitation. No wasted words, earns its place.

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

Completeness3/5

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

For a 3-parameter tool with no output schema, the description is adequate but incomplete. It lacks specifics on output format (e.g., list of BibTeX strings) and error handling (invalid queries, empty results).

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 baseline is 3. The description adds context about ranking that complements the 'exactTitle' and 'maxResults' parameters, enhancing understanding beyond individual schema descriptions.

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 verb 'Search', the resource 'Google Scholar', and the output ('multiple BibTeX options'). It specifies ranking preference and limitations, distinguishing it from generic search tools.

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?

No sibling tools are provided, so differentiation is not required. The description implies usage when a BibTeX citation from Google Scholar is needed, but lacks explicit guidance on when not to use or prerequisites.

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

Deploy Server

Other Tools

google_scholar_bibtexA