Skip to main content
Glama
Sign In
scipdf-mcp

scipdf-mcp

by gjjisadog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

format_citation

Fetch Crossref metadata for a given DOI and generate a citation in APA, GB/T 7714, or BibTeX format.

Instructions

Format APA / GB/T 7714 / BibTeX from DOI (fetches Crossref metadata).

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": "format_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiYesDOI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that Crossref metadata is fetched, but lacks details on error handling, rate limits, or whether network access is required.

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 a single, well-structured sentence that conveys all essential information without any waste.

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 tool with one parameter and no output schema, the description adequately explains the function but does not specify the return format or behavior with invalid DOIs, leaving some gaps.

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% with the 'doi' parameter described as 'DOI'. The description adds value by explaining that the DOI is used to fetch Crossref metadata, enhancing the schema's minimal description.

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 tool formats citations in specific styles (APA, GB/T 7714, BibTeX) using a DOI, which distinguishes it from siblings like resolve_doi or download_paper.

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?

The description implies usage when a DOI is available by mentioning 'from DOI', but does not explicitly state when to use this tool over alternatives like parse_references or when not to use it.

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