Skip to main content
Glama

Delete a food entry

trainrec_delete_food
Destructive

Removes one food entry, given its id and version. The person can undo it in the app.

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": {
      "id": "<id>",
      "version": "<version>"
    },
    "name": "trainrec_delete_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real value beyond them: it scopes the destruction to exactly one entry and discloses that the deletion is reversible in the app. It does not explain what happens on a version mismatch or whether there is a recovery window, which would complete the picture.

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, front-loaded with the action and scope, with the reversibility note placed after. No filler, no repetition of the title or schema.

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 two-required-parameter destructive tool with no output schema, the description covers scope, both inputs by name, and reversibility, which is adequate. It still leaves the agent guessing about version-mismatch behavior and confirmation requirements, gaps that matter for a delete operation.

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 0%, so the description must carry parameter meaning, and it names both parameters ('id and version') while the schema gives only types. However, it never explains what 'version' is for, leaving the likely optimistic-concurrency semantics unstated for a required parameter the agent must supply correctly.

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 uses a specific verb ('Removes') on a specific resource ('one food entry'), which is unambiguous and clearly distinct from logging or editing a food entry. It does not explicitly name or contrast with siblings such as trainrec_edit_food or trainrec_undo_change, so it stops short of full differentiation.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this versus editing an entry or using the undo tool; the reader must infer that deletion is the right action when the entry should no longer exist. The note that the user can undo it in the app is the only adjacent context, and it points at the app rather than a sibling tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources