Skip to main content
Glama
Sign In

Dandori

by life.dandori
OverviewDiscussionsAdmin

Écrire dans Mon journal

dandori_journal_write

Écrire une entrée dans Mon journal, seulement quand l'utilisateur le demande. Le journal n'est jamais lisible par l'IA : l'entrée ne pourra être ni relue, ni modifiée, ni supprimée par un outil.

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": {
      "content": "<content>"
    },
    "name": "dandori_journal_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate de l'entrée (YYYY-MM-DD, défaut aujourd'hui, jamais dans le futur)
moodNoHumeur du moment (ex. emoji ou texte court)
typeNoType d'entrée (free = libre, word = 1 mot, phrase = 1 phrase)
contentYesContenu de l'entrée

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses significant traits: the journal is never readable by the AI and the entry can be neither reread, edited, nor deleted by any tool. That permanence and privacy context is exactly the kind of information an agent needs before writing. It does not address idempotency or what the call returns, which keeps it from a 5.

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?

Two short sentences with zero waste; the usage constraint and the critical irreversibility warning are both front-loaded. Nothing repeats the name or the schema.

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 four-parameter, fully documented write tool with annotations supplied and no output schema, the description covers what matters: when to call it and that the write is final and unreadable. A note on the confirmation returned by the call would make it fully complete.

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 description coverage is 100%, so the date, mood, type enum and content parameters are already fully documented in structured form. The description adds no parameter-level meaning such as defaulting rules or how 'mood' interacts with entry 'type', so the baseline 3 applies.

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 names a specific verb and resource ('Écrire une entrée dans Mon journal'), so the agent knows exactly what the tool does. It does not explicitly contrast itself with siblings such as dandori_create_note, leaving the journal-vs-note distinction to be inferred from the possessive 'Mon journal'.

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 a clear, explicit gating condition: write only when the user requests it. It stops short of naming alternatives (e.g. a note or quote tool) for cases where the user wants something other than a private journal entry.

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

All Dandori toolsInspect
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