Skip to main content
Glama

adb_registry_installed

List locally installed plugins with versions and metadata to identify which have updates available in the registry.

Instructions

List all locally installed plugins with their versions and metadata. Shows which plugins have updates available in the registry.

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_registry_installed"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It implicitly signals a read-only listing and discloses a meaningful behavioral trait — that results include update-availability computed against the registry — but it never says whether reaching the registry requires network access, whether the device must be connected, or whether metadata is cached or freshly fetched.

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, zero padding, with the core purpose front-loaded and the update-availability detail as a useful follow-on. Nothing here is restated from the name or schema.

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 trivial zero-parameter tool with no output schema, describing the returned contents (versions, metadata, update flags) is exactly the compensation needed. The remaining gap is routing clarity against adb_plugin_list and the other registry siblings, which matters in a toolset of this size.

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?

The tool takes zero parameters, so baseline is 4. The description adds that the output is scoped to locally installed plugins rather than the whole registry, which is the only semantically relevant constraint for a no-argument tool.

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 ("List all locally installed plugins") and names the payload fields (versions, metadata, update availability). It is nearly distinct from registry-oriented siblings like adb_registry_search, but it never clarifies how it relates to the very similar-sounding adb_plugin_list, leaving a real disambiguation gap.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for checking what's installed locally and whether updates exist. There is no explicit when-to-use, no statement that it requires no registry arguments (unlike adb_registry_search or adb_registry_install), and no exclusion of the confusable adb_plugin_list.

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