Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_agent_note

Destructive

Delete a stored agent note or preference by key and scope, optionally targeting a printer-specific namespace.

Instructions

Remove a stored note or preference.

        Args:
            key: The key of the note to delete.
            scope: The scope namespace (default ``"global"``).
            printer_name: If provided, targets ``"printer:<name>"`` scope.

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": {
      "key": "<key>"
    },
    "name": "delete_agent_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe key of the note to delete.
scopeNoThe scope namespace (default ``"global"``). Default: "global".
printer_nameNoIf provided, targets ``"printer:<name>"`` scope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / key / description
      Added value: +"The key of the note to delete."
    • addedInput schema / properties / printer_name / description
      Added value: +"If provided, targets ``\"printer:<name>\"`` scope."
    • changedInput schema / properties / scope / description
      Previous value: -"Default: \"global\"."New value: +"The scope namespace (default ``\"global\"``). Default: \"global\"."
  2. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / printer_name / default
      Removed value: -null
    • removedInput schema / properties / scope / default
      Removed value: -"global"
    • addedInput schema / properties / scope / description
      Added value: +"Default: \"global\"."
  3. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the scope model (global default, 'printer:<name>' targeting), which is genuinely useful behavior. It does not say whether deletion is idempotent, what happens if the key is absent, or whether scope and printer_name conflict.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is tight and front-loaded, but the Args block duplicates the input schema word-for-word, which is dead weight rather than added value. Roughly half the text earns nothing beyond what structured fields already provide.

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 three-parameter destructive delete with no output schema, the description covers the call shape adequately but omits error/absence behavior and the precedence between scope and printer_name. An agent could invoke it, but not predict the outcome of edge cases.

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% and the Args block restates the schema descriptions almost verbatim, adding essentially no new meaning. Baseline 3 applies because the schema already carries the parameter documentation.

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?

States a specific verb and resource ('Remove a stored note or preference'), which is unambiguous. However it never distinguishes this from closely related siblings such as save_agent_note or clean_agent_memory, so an agent must infer the boundary from the name alone.

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 guidance on when to delete versus when to save or when to use clean_agent_memory for bulk removal, and no prerequisites or caveats are given. The description is purely a mechanical description of the call.

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