Skip to main content
Glama

TrueInterview

Delete a note kept for me

delete_context_note
DestructiveIdempotent

Delete one of the notes kept for the candidate, by an id list_context_notes or save_context_note returned, when they ask you to or tell you it is no longer true. It is gone for good. Only these notes can be deleted here: no other record of theirs is ever removed by this server.

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": {
      "note_id": "<note_id>"
    },
    "name": "delete_context_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is largely structured. The description still adds value beyond them by spelling out permanence ('It is gone for good') and the explicit scoping guarantee that no other record of the candidate's is affected, which is not derivable from the annotations.

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 action and resource, then the trigger, then the permanence and scope caveats. No filler or repeated information.

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 one-parameter destructive delete with no output schema, the description covers what is removed, where the id comes from, that the effect is irreversible, and that nothing else is affected. That is everything an agent needs to call it correctly.

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 0% and the schema itself only constrains the UUID format, so the description carries the burden for the single parameter. It does so by naming the two tools whose return values supply the note_id, giving the agent provenance for the value rather than just a type.

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 (delete) and a specific resource (notes kept for the candidate), and identifies the exact source of the identifier: an id returned by list_context_notes or save_context_note. It is clearly distinguishable from those siblings, which read and write rather than remove.

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

Usage Guidelines4/5

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

Gives concrete trigger conditions: the candidate asks for deletion, or tells you the note is no longer true. It also bounds scope by stating no other record of theirs is ever removed here. It lacks any caution about confirming with the user before an irreversible delete, which would be the remaining piece of guidance for a destructive 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