Skip to main content
Glama
Sign In

siftivo

by com.siftivo
OverviewDiscussionsAdmin

Delete a journal entry

delete_journal_entry
DestructiveIdempotent

Delete one day's entry for one book from the linked reader's journal, note and position together. The book stays on its shelf where it was. Suits "delete what I wrote about X yesterday". To change a day's note, write_journal with replaceNote. Needs a linked Siftivo account.

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": {
      "book": "<book>",
      "date": "<date>"
    },
    "name": "delete_journal_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYesA title, "Title by Author", or a workId
dateYesA day in the reader's own time zone, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this destructive, idempotent, and non-read-only, so the safety profile is covered. The description adds value beyond them by bounding the destruction ("note and position together" while "the book stays on its shelf where it was") and by naming the account-link requirement, though it says nothing about what a deletion returns or how a missing entry is handled.

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?

Roughly four short sentences, front-loaded with the action and scope, then the non-destruction guarantee, then the alternative and prerequisite. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool with full schema coverage and no output schema, the description covers action, deletion scope, what is preserved, the alternative, and the account prerequisite. Nothing an agent needs to call it correctly is missing.

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 100%, so both parameters are already documented with format and time-zone semantics. The description reinforces that it is one entry for one book on one date but adds no syntax or edge-case meaning beyond the schema, which is the expected baseline here.

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

Purpose5/5

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

The description opens with a specific verb+resource+scope: delete one day's entry for one book from the reader's journal, removing note and position together. It also implicitly distinguishes itself from write_journal by naming it for the different task, so an agent can pick between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete usage scenario ("delete what I wrote about X yesterday"), an explicit alternative for a nearby-but-different task (write_journal with replaceNote), and a prerequisite (a linked Siftivo account). When-to-use, when-to-use-something-else, and eligibility are all stated.

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

All siftivo 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