Dandori

Créer ou modifier une lecture

dandori_save_learning_item

Créer une lecture (sans id, title obligatoire) ou la modifier (avec id ; seuls les champs fournis changent). Passer à finished la termine. Sans Plus, le nombre est limité (le refus le dit).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dandori_save_learning_item"
  }
}

Input Schema

Name	Required	Description
`id`	No	ID de la lecture à modifier ; absent pour en créer une
`type`	No	book, manga, comic (BD), course, podcast, video ou article ; manga et comic sont des séries, comptées en tomes
`title`	No	Titre (obligatoire à la création)
`author`	No
`rating`	No	Note de 1 à 5
`status`	No	wishlist (une envie, pas encore possédée), to_read, in_progress, finished ou abandoned
`category`	No
`language`	No	Langue (ex. fr)
`cover_url`	No	Adresse de la couverture ; celle que donne la recherche au catalogue (dandori_list_learning, catalog_title)
`started_at`	No	Début (YYYY-MM-DD)
`finished_at`	No	Fin (YYYY-MM-DD)
`series_ended`	No	Série : parution terminée (plus de tome à paraître)
`volumes_read`	No	Série : numéros des tomes lus, la liste entière
`volumes_owned`	No	Série : numéros des tomes possédés, la liste entière (ex. [1, 2, 3, 5]) ; pour en ajouter à une série existante, dandori_action mark_learning_volumes
`personal_notes`	No
`progress_total`	No	Total (pages, leçons, épisodes…) ; pour une série, les tomes parus
`progress_current`	No	Où on en est, dans la même unité ; pour une série, le nombre de tomes lus (les premiers)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare it is a non-read-only, non-idempotent, non-destructive write. The description adds genuine behavior: patch semantics (only provided fields change), the side effect that setting status to `finished` closes the item, and a quota that can reject the call with an explanatory refusal on plans without Plus.

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?

Three compact clauses, front-loaded with the create/update decision, with no filler. The phrase 'Sans Plus' is unexplained plan jargon that an agent may not resolve without external knowledge, which slightly undercuts the terseness.

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?

For a 17-parameter mutation with no output schema, the description covers create/update modes, partial updates and quota, which is the core. It says nothing about what the call returns (e.g. the new item's id) or about how the many series/progress fields interact, leaving gaps for a schema this large.

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

Parameters3/5

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

Schema coverage is 82%, so the schema already documents nearly every field, including enum meanings and the series/tomes rules. The description only reinforces the `id`/`title`/`status` semantics that the schema already spells out, adding little new parameter meaning.

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 states a concrete verb and resource ('Créer une lecture … ou la modifier') and clearly branches on the presence of `id`, so the two operating modes are distinguishable. It does not name any sibling tool, so an agent must infer on its own that list items, quotes, or sessions live elsewhere.

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?

It gives explicit conditions: omit `id` to create (with `title` mandatory), supply `id` to modify, and only supplied fields change. It also flags the `finished` transition and a plan-based quota refusal, which is real when-to-use context, but it never names an alternative tool for the adjacent operations.

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

All Dandori tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?