Academic Writer MCP

Importer des notices (RIS / BibTeX)

import_sources_file

Import multiple RIS or BibTeX sources at once, save and locally verify each entry, and automatically skip duplicates.

Instructions

Importe en une fois les notices d'un fichier RIS ou BibTeX : chaque source est enregistrée et vérifiée localement ; les doublons sont ignorés.

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": {
      "project_id": "<project_id>",
      "file_path": "<file_path>"
    },
    "name": "import_sources_file"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Chemin absolu d'un fichier .ris ou .bib exporté depuis un catalogue (Zotero, Google Scholar, eLIBRARY, РГБ, bibliothèque…).
`project_id`	Yes

Output Schema

Name	Required	Description
`file`	Yes
`found`	Yes
`errors`	Yes
`format`	Yes
`message`	Yes
`imported`	Yes
`duplicates`	Yes	Notices déjà présentes dans le projet (non réimportées).
`project_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the annotations' general write and non-destructive profile, the description discloses that sources are verified locally and duplicates are ignored. It does not explain what verification checks, how duplicates are matched, or whether errors can produce a partial import, but the disclosed behaviors are useful for predicting effects.

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 single compact sentence front-loads the operation, input formats, and bulk scope, then adds two consequential behaviors. There is no filler or redundant structural wording.

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?

For a simple two-parameter import with safety annotations and an output schema, the definition supplies enough information to understand and generally invoke the operation correctly. It remains incomplete on destination-project semantics, duplicate detection, local verification, and partial-failure behavior, none of which must be inferred from the output schema.

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?

The description largely repeats the RIS/BibTeX file information already supplied by file_path's schema description and adds no new path semantics. The required project_id lacks a schema description, and the description does not clarify that it identifies the destination project or state any related constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action and resource: batch-importing bibliographic records from a RIS or BibTeX file and saving each one as a source. Its focus on bibliographic records gives some separation from document-oriented siblings, but it does not explicitly delineate that boundary or name an alternative.

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 supported formats and phrase "en une fois" imply that this is for one-shot bulk imports of existing bibliography files. However, there is no explicit when-to-use guidance, prerequisite, exclusion, or routing to another workflow such as import_document when the input is not a RIS/BibTeX bibliography.

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

Deploy Server