Skip to main content
Glama

adb_result_get

Retrieve stored result content by source tool and handle name, returning the original content blocks and updating the handle's last-accessed time.

Instructions

Retrieve the content of a stored result handle by tool name + handle name. Returns the original content blocks as the source tool produced them. Updates the handle's last-accessed time. For URI-based retrieval, read result://<tool>/<name> as an MCP Resource instead.

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": {
      "tool": "<tool>",
      "name": "<name>"
    },
    "name": "adb_result_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHandle name supplied at storage time (e.g., 'initial')
toolYesSource tool name (the tool that originally stored the handle, e.g., 'bugreport')

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

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does disclose real behavior: the payload is returned exactly as the source tool produced it, and the call mutates the handle's last-accessed timestamp — a side effect an agent would not otherwise expect from a read. It omits failure behavior for unknown or expired handles, which is the remaining gap for a zero-annotation tool.

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 tight sentences: what it returns, the side effect, then the alternative access method. Nothing is repeated and the core action is front-loaded.

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 two-parameter read with no output schema, the description covers the return shape ('original content blocks') and the URI alternative, which is enough for an agent to call it correctly. Handle lifecycle details (expiry, missing-handle errors) are the only notable omission.

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 100% and both parameters already document their role with examples ('bugreport', 'initial'), so the description only restates the composite key. It adds no new format, case-sensitivity, or scoping detail beyond what the schema provides, which is the expected baseline here.

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 gives a specific verb and resource ('Retrieve the content of a stored result handle') plus the exact lookup key (tool name + handle name), so the operation is unambiguous. It does not explicitly name the closely related siblings adb_result_list and adb_result_drop, so sibling differentiation is only implied by the verb.

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?

It states the primary use case (fetch a stored handle's payload) and names a concrete alternative path for URI-based access via the MCP Resource result://<tool>/<name>. It stops short of saying when a handle is preferable to re-running the source tool, or what to do when a handle is missing.

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