Skip to main content
Glama
pallaprolus

mendeley-mcp

by pallaprolus
OverviewSchemaRelated ServersScoreDiscussions
Python

mendeley_add_document

Add academic documents to your Mendeley reference library by providing title, authors, publication details, and identifiers for organized research management.

Instructions

Add a new document to your Mendeley library.

Args:
    title: Document title (required)
    doc_type: Type - 'journal', 'book', 'conference_proceedings', etc.
    authors: List of author dicts with 'first_name' and 'last_name'
    year: Publication year
    source: Journal/book name
    abstract: Document abstract
    identifiers: Dict with 'doi', 'pmid', 'isbn', etc.

Returns:
    JSON object with the created document

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
doc_typeNojournal
authorsNo
yearNo
sourceNo
abstractNo
identifiersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a creation operation ('Add a new document'), it doesn't disclose important behavioral traits like authentication requirements, rate limits, whether duplicates are allowed, what happens on failure, or how the document integrates with the library structure. The description mentions the return format but lacks operational context.

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 well-structured with clear sections (purpose, args, returns) and uses bullet-like formatting for parameters. Every sentence adds value, though the parameter explanations could be slightly more concise. The front-loaded purpose statement is clear, making it easy to scan and understand the tool's function quickly.

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?

Given the tool's complexity (7 parameters, creation operation) and the presence of an output schema (which handles return values), the description is moderately complete. It excels at parameter documentation but lacks behavioral context that would be crucial for a mutation tool with no annotations. The description doesn't address error conditions, permissions, or integration with the broader Mendeley ecosystem.

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

Parameters5/5

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

The description provides excellent parameter semantics beyond the input schema, which has 0% description coverage. For all 7 parameters, it adds meaningful context: clarifying that 'title' is required, explaining 'doc_type' with examples, detailing the structure of 'authors' dicts, and specifying what 'identifiers' can contain. This fully compensates for the schema's lack of descriptions.

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 specific action ('Add a new document') and target resource ('to your Mendeley library'), distinguishing it from sibling tools that retrieve, list, or search documents rather than create them. The verb+resource combination is precise and unambiguous.

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 like 'mendeley_search_catalog' for finding existing documents or 'mendeley_list_documents' for viewing the library. There's no mention of prerequisites, constraints, or typical use cases for adding documents versus using other tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pallaprolus/mendeley-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server