Skip to main content
Glama

adb_result_drop

Deletes a stored result handle or clears all handles in the current session, helping free store capacity or remove stale data before sensitive operations.

Instructions

Delete a stored result handle, or clear all handles in this session. Either provide both tool and name to drop one specific handle, or pass all: true to drop everything in the current namespace. Useful for freeing up the store cap proactively or removing stale data before a sensitive operation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_result_drop"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoIf true, delete every handle in this namespace. tool/name must be omitted when all=true.
nameNoHandle name (required unless all=true)
toolNoSource tool name (required unless all=true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.1.3

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the important behavior: this is a destructive delete, its scope is limited to the current session/namespace, and it can free the store cap. It omits error behavior for a nonexistent handle and whether the operation is idempotent or returns a count.

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

Conciseness4/5

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

Three short sentences: purpose first, the two modes second, rationale last — a sensible front-loaded order. The mode sentence duplicates constraints already in the schema, which costs a little density.

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?

For a three-parameter, no-output-schema tool with zero annotations, the definition covers what is deleted, at what scope, and why. Only the return value/pagination-free result of the delete and error cases are unaddressed, which is a minor gap.

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 the mutual exclusivity rule (tool/name omitted when all=true) is already documented in the parameter descriptions. The description restates the pairing rather than adding new semantics, so it sits at the baseline for a fully documented schema.

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?

Uses a specific verb+resource pair ("Delete a stored result handle") plus a clearly stated second mode ("clear all handles in this session"). It is easily distinguished from adb_result_list/adb_result_get by intent, though it never names those siblings to reinforce the boundary.

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 explicit invocation conditions: both `tool` and `name` for a single handle, or `all: true` for everything in the namespace. It also motivates use ("freeing up the store cap proactively", "removing stale data before a sensitive operation") but offers no explicit exclusion telling the agent when to read rather than drop.

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