Skip to main content
Glama
science-ai-mcp-server

science-ai-mcp-server

by SelfPy

Check Duplicate Publication

check_duplicate_publication

Checks a paper title against external sources and a local library to detect duplicate publications or preprints before submission, returning match status and confidence.

Instructions

Pre-submission duplicate-publication check: has this paper already been published? Checks 7 external sources — CrossRef, PubMed, arXiv, bioRxiv, medRxiv and Europe PMC by title (an abstract, when given, is used to confirm close matches), and Unpaywall by DOI (so only when you pass one) — plus a 7.9M-paper local library, all queried in parallel with a 12-second cap per source. Returns a status — likely_published, preprint_found (the match is a preprint, not a journal article), uncertain (a possible match), not_found, or unable_to_check (no source could be reached) — with a message and, on a match, a link and a confidence score where the source gives one. A not_found that could not reach some sources says which. Free — spends no credits. Rate-limited per account (an API key counts against its account); a 429 says when to retry. Use before submission to catch an accidental duplicate or to see whether a preprint has since been formally published.

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

Input Schema

NameRequiredDescriptionDefault
doiNoKnown DOI for the paper, if any.
titleYesPaper title (required).
abstractNoPaper abstract — improves match accuracy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: parallel querying, a 12-second cap per source, cost ('Free — spends no credits'), per-account rate limiting with 429 retry semantics, and partial-failure reporting ('A not_found that could not reach some sources says which'). It also pre-explains the full status taxonomy including the ambiguous cases uncertain and unable_to_check.

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

Conciseness4/5

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

Front-loaded with the question being answered, then sources, then return values, then cost/limits — a logical order. It is dense and long for one paragraph, and the em-dash-interleaved source list takes effort to parse, but almost every clause carries operational information.

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

Completeness5/5

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

No output schema exists, yet the description fully specifies the return shape: status enumeration with definitions, message, link and confidence score on a match, plus the caveat that not_found may flag unreachable sources. For a three-parameter read tool with no annotations, nothing an agent needs in order to call or interpret it is missing.

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 schema baseline already documents all three fields, but the description adds meaningful routing semantics: title drives the six bibliographic sources, abstract is used only to confirm close matches, and DOI gates Unpaywall entirely. That is genuine meaning beyond the schema's field-level descriptions, though it stops short of format examples.

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?

States a specific verb and resource ('Pre-submission duplicate-publication check: has this paper already been published?') and enumerates exactly what it consults — CrossRef, PubMed, arXiv, bioRxiv, medRxiv, Europe PMC by title, Unpaywall by DOI, plus a local library. An agent can distinguish this from a generic pre-check sibling purely from the description.

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?

Gives clear timing and intent: 'Use before submission to catch an accidental duplicate or to see whether a preprint has since been formally published.' It also clarifies the conditional nature of the DOI path ('so only when you pass one'). It does not name the sibling pre_check_paper or say when to prefer it, so no explicit alternatives or exclusions.

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