Skip to main content
Glama
Sign In
zotero-mcp

zotero-mcp

by masaki39
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

confirm_doi

Validates a DOI by retrieving its metadata from CrossRef, ensuring it exists before adding to Zotero.

Instructions

Fetch metadata for a DOI from CrossRef to validate it exists before adding to Zotero.

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

Input Schema

NameRequiredDescriptionDefault
doiYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavior. It mentions fetching metadata and validating existence but does not explain what happens if the DOI is invalid, what metadata is returned, or any side effects (e.g., network requests, rate limits). This is insufficient for a tool with no annotations.

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?

The description is extremely concise at one sentence, front-loading the action and purpose. It is efficient but loses a point for being too brief, sacrificing helpful details.

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

Completeness2/5

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

Given the low complexity (one parameter, no output schema, no annotations), the description is incomplete. It does not cover error handling, return value, prerequisites, or authentication needs. A validation tool should at least explain the expected outcome (e.g., status or metadata).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It mentions 'a DOI' as the parameter, which adds minimal meaning beyond the schema. It does not provide format examples, restrictions, or guidance on values, leaving the agent underinformed.

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 verb 'Fetch metadata', the resource 'DOI from CrossRef', and the purpose 'to validate it exists before adding to Zotero'. It effectively distinguishes this tool from siblings like 'add_item_by_doi' which presumably adds the item after validation.

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?

The description implies this tool should be used before adding to Zotero, providing clear context. However, it does not explicitly state when not to use it or mention alternatives, though the sibling list gives some guidance.

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