Skip to main content
Glama

adb_registry_install

Install a community registry plugin by name by downloading its JavaScript file into the plugins directory. Restart DeepADB afterward to load the new plugin.

Instructions

Install a plugin from the community registry by name. Downloads the plugin JavaScript file into the plugins directory. Restart DeepADB to load it.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPlugin name from the registry
forceNoOverwrite if already installed

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. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does contribute real behavior: the plugin is downloaded as a JS file into the plugins directory and requires a DeepADB restart to take effect. It omits what happens on name-not-found, whether the download hits the network, permission requirements, and that the 'force' path overwrites an existing install.

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, front-loaded with the action, then two operational facts. No filler; the restart note earns its place as actionable follow-up.

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 install tool with no annotations and no output schema, the description covers what it does, where files land, and the required restart. The remaining gaps (failure modes, install location specifics, auth) are modest for this complexity.

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 both 'name' and 'force' are already documented in the schema. The description only reinforces that the name comes from the registry and says nothing about the overwrite flag, so baseline 3 applies.

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 plus the source ('Install a plugin from the community registry by name') and clarifies the payload is a JavaScript file, which separates it from the APK-oriented adb_install. It never names a sibling explicitly, so the distinction is inferable rather than stated.

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?

Implies usage via 'by name' and the restart instruction, so an agent can infer it should call adb_registry_search first to obtain a valid name. It never says when to use this versus adb_market_install, adb_plugin_list, or adb_registry_installed, and gives no prerequisites or exclusions.

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