Skip to main content
Glama
Sign In

whatevr

by app.trywhatevr
OverviewDiscussionsAdmin

delete_log

Destructive

Delete ONE entry from the user's log: a food, exercise, weigh-in or water entry. Read get_today/get_day first — each item in recent carries its id and type; pass both. Deleting a weigh-in updates their current weight to the newest remaining one. This can't be undone, so confirm with the user first. Needs the user's "Delete entries" switch for this connection (whatevr app → Settings → Connections). The user is notified.

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": {
      "log_id": "<log_id>",
      "type": "<type>"
    },
    "name": "delete_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe item's `type` from `recent`.
log_idYesThe item's `id` from get_today/get_day `recent`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes well beyond: irreversibility, the side effect that deleting a weigh-in rewrites current weight, a permission gate ('Delete entries' switch) with the exact UI path, and the notification side effect. That is precisely the extra context annotations cannot carry.

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?

Five short sentences, each carrying distinct load: scope, prerequisite, side effect, irreversibility, permission. The destructive warning and read-first instruction are front-loaded before the permission detail.

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?

Covers prerequisites, side effects, permissions and irreversibility for a two-param destructive tool with no output schema. The one unaddressed gap is failure behavior — what the agent should do if the id no longer exists.

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 is 3, but the description adds provenance the schema lacks — `type` and `log_id` must be taken from the `recent` array of get_today/get_day and passed together. It stops short of stating what happens if the id is stale or already deleted.

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?

States a specific verb and resource with explicit scope: 'Delete ONE entry from the user's log', enumerating the four entry kinds. This cleanly separates it from update_log (modify) and the log_* siblings (create) without the agent needing to open any 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?

Gives an explicit prerequisite workflow ('Read get_today/get_day first'), names the exact fields to source from `recent`, and adds a procedural guard ('confirm with the user first'). Alternatives and the when-not condition are all covered.

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

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