Skip to main content
Glama
Sign In
BioCite-MCP

BioCite-MCP

by muslus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_duplicate_citations

Detect duplicate citations in a list by comparing DOIs and title similarity. Set a threshold to control matching sensitivity.

Instructions

Identify duplicate papers in a list based on DOI and Title similarity.

Args: papers_json: A JSON string containing a list of paper objects with 'title' and optional 'doi'. threshold: Similarity threshold (0-100) for title matching.

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": {
      "papers_json": "<papers_json>"
    },
    "name": "check_duplicate_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
papers_jsonYes
thresholdNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behavior. It mentions the matching criteria but does not specify output format, side effects, or whether the tool is read-only. The default threshold is noted but lacks explanation of consequences.

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 concise with two sentences: the first states the purpose, the second lists parameters. No waste, front-loaded with key 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?

With an output schema present, the description does not need to explain return values. It adequately covers parameters but lacks context about when to use. Given low complexity, it is sufficiently complete.

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?

The description adds meaning by explaining the structure of 'papers_json' (list of objects with 'title' and optional 'doi') and the range of 'threshold' (0-100). This compensates for the 0% schema description coverage.

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 identifies duplicate papers based on DOI and title similarity, using specific verbs and resources. It distinguishes from sibling tools like 'find_related_papers' by focusing on duplicates.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or typical use cases.

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