Skip to main content
Glama
dsh-lit-search-mcp

dsh-lit-search-mcp

by Flan246

lit_bib

Read-onlyIdempotent

Generate BibTeX entries from a list of DOIs, returning combined .bib content and any DOIs that failed.

Instructions

Generate BibTeX entries for a list of DOIs. Returns combined .bib content and the list of DOIs that failed.

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": {
      "dois": "<dois>"
    },
    "name": "lit_bib"
  }
}

Input Schema

NameRequiredDescriptionDefault
doisYesArray of DOI strings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the description's contribution is the return semantics: combined .bib content plus the list of failed DOIs. That partial-failure disclosure is genuinely useful and not derivable from annotations. It stops short of explaining retry behavior or how failures are represented.

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 short sentences, no filler, and the core action is front-loaded before the return-value note. Every clause carries information.

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 one-parameter read tool with rich annotations, the definition covers both the action and the shape of the response, including failure reporting. Minor gaps remain around volume limits or how to interpret a partial result, but nothing critical is missing for correct invocation.

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?

There is a single parameter with 100% schema description coverage ('Array of DOI strings'), so the schema already does the work. The description's phrase 'for a list of DOIs' adds no syntax, format, or ordering detail beyond the schema, which matches the baseline 3 for high coverage.

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 and resource ('Generate BibTeX entries') plus the input shape ('for a list of DOIs'). It is clear what the tool does, but it gives no signal distinguishing it from the sibling lit_cite, which an agent could reasonably confuse it with.

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?

Usage is only implied: you have DOIs and want BibTeX. There is no explicit when-to-use, no when-not-to-use, and no routing to or from the sibling tools like lit_cite or lit_search.

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