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

dsh-lit-search-mcp

by Flan246

lit_cite

Read-onlyIdempotent

Format a DOI into a citation in GB/T 7714, GB/T 7714 numeric, APA, or BibTeX style to generate references for papers and bibliographies.

Instructions

Format a citation for a DOI. Styles: gbt7714 (Chinese standard), gbt7714-numeric (numbered), apa, bibtex.

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": {
      "doi": "<doi>"
    },
    "name": "lit_cite"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiYesPaper DOI
styleNogbt7714 | gbt7714-numeric | apa | bibtex (default gbt7714)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds that multiple output styles are supported and implies a single citation string is produced, but says nothing about behavior for unresolvable DOIs or network lookup failures, which is relevant given openWorldHint=true.

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 sentences, zero filler, with the action front-loaded and the style list immediately after. Every clause carries information the agent needs.

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 two-parameter, single-purpose tool with rich annotations, this is nearly complete; the return value is self-evident from 'Format a citation'. The only shortfall is the absence of any note on failure behavior when a DOI cannot be resolved during the open-world lookup.

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 the baseline is 3, but the description adds real meaning beyond the raw enum values by glossing 'gbt7714' as the Chinese standard and 'gbt7714-numeric' as numbered output. The 'doi' parameter is left to the schema's 'Paper DOI' label, which is adequate for such a simple field.

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?

The description opens with a specific verb+resource pair ('Format a citation for a DOI'), which is unambiguous. It does not explicitly differentiate itself from siblings like lit_bib, but the purpose is narrow enough that an agent can select it without opening the schema.

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?

Usage is implied by the purpose (you have a DOI and need a formatted citation), and the style list hints at when each output form is appropriate. There is no explicit when-not-to-use guidance or routing to lit_bib for bibliography-level operations.

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