Skip to main content
Glama
Sign In
dev-diary-mcp

dev-diary-mcp

by rogeriolaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

edit_entry

Update an existing diary entry's text by date and time, select an occurrence for duplicate times, and omit tags to keep existing labels.

Instructions

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

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>",
      "text": "<text>"
    },
    "name": "edit_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesISO date of the entry
tagsNoNew labels; omit to keep existing tags
textYesNew entry text
timeYesTime of the entry (HH:MM)
occurrenceNoWhich entry with that time (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key mutation semantics that the operation is a full replace rather than a patch, and that omitting tags preserves existing tags. It does not say what happens if no entry matches the date/time (error vs. create), whether the change is reversible, or what is returned.

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?

Three short sentences, front-loaded with the identification requirement, followed by the disambiguation rule and the tags default. Nothing extraneous and no repetition of boilerplate.

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 five-parameter mutation tool with no annotations and no output schema, the description covers identification, disambiguation, and tag semantics but leaves notable gaps: behavior when the entry does not exist, and any indication of what the call returns or whether the previous content is recoverable.

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 description coverage is 100%, so the baseline is 3; the description goes slightly beyond by explaining the tie-breaking purpose of occurrence (1-based selection among same-time entries) and reinforcing the omit-tags default, though both points are already stated in the schema property descriptions.

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 opens with a specific verb and resource, 'Replace an existing entry', and states the identifier (date plus HH:MM time). It is clearly distinguishable from siblings like delete_entry and log_work, though it never names them 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?

Use is implied by 'Replace an existing entry' - an agent can infer that new entries go through log_work and removals through delete_entry - but the description never states when to prefer this tool over those siblings or any prerequisites.

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

Deploy Server

Other Tools