dev-diary-mcp

Overview Schema Source Related Servers Discussions Admin

delete_entry

Remove a diary entry by its ISO date and HH:MM time; when multiple entries share that time, specify the 1-based occurrence to delete the intended one.

Instructions

Remove an existing entry identified by date and time (HH:MM). If several entries share the same time, use occurrence to pick one (1-based).

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": {
      "date": "<date>",
      "time": "<time>"
    },
    "name": "delete_entry"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	ISO date of the entry
`time`	Yes	Time of the entry (HH:MM)
`occurrence`	No	Which entry with that time (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add genuinely useful behavior for the ambiguity case (multiple entries at the same time, resolved via `occurrence`), but it never says whether deletion is permanent, what happens if no entry matches, or what errors look like — significant omissions for a destructive operation.

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 sentences, front-loaded with the action and identifier, then the edge-case rule. No filler and nothing redundant.

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 three-parameter delete tool with no annotations and no output schema, the description should at minimum signal irreversibility and failure behavior. It covers identification and disambiguation well but leaves the agent without the information needed to judge consequences before calling.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description goes further by explaining the real-world condition under which `occurrence` matters (collisions on the same time) and confirming it is 1-based. That adds meaning beyond the schema's terse "Which entry with that time".

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?

States a specific verb and resource ("Remove an existing entry") plus the identifier used to select it (date and time in HH:MM). An agent can distinguish it from edit_entry and log_work, but the description never names those siblings or contrasts the operations explicitly.

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?

Usage is only implied by the verb "Remove"; there is no statement of when deletion is appropriate versus editing, and no suggestion to locate the entry first (e.g. via search_diary) before deleting. Adequate but leaves routing to inference.

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

Deploy Server