Skip to main content
Glama

adb_registry_search

Search the community plugin registry by keyword to find available plugins and view their names, descriptions, versions, and authors.

Instructions

Search the community plugin registry for available plugins. Shows name, description, version, and author. Fetches the latest manifest from the configured registry URL.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFilter plugins by name or description keyword

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 burden, and it does disclose two useful traits: the returned fields and that it fetches a live manifest from a configured registry URL (i.e., a network-dependent read). It omits result limits, pagination, offline/failure behavior, and caching, which matter for a remote fetch.

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 with the core action front-loaded and no filler; each sentence contributes purpose, return shape, or data source. Slightly more compressed phrasing could merge the return-field and manifest sentences, but nothing is wasted.

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 one-optional-parameter read tool with no output schema, listing the returned fields plus the manifest source covers what an agent needs to call it and interpret results. The remaining gap is behavioral edge cases (network failure, result cap), which is minor at 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 description coverage is 100% for the single optional query parameter, so the baseline is 3. The description adds no meaning beyond the schema — it does not say whether an empty query returns everything, whether matching is case-insensitive, or whether it matches author/version too.

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 ("Search the community plugin registry for available plugins") and names the four fields returned. That distinguishes it from install/mutation siblings like adb_registry_install and from adb_plugin_list / adb_market_search, though it never names those alternatives explicitly.

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 discovery step before adb_registry_install, but the description never says when to use it versus adb_plugin_list, adb_registry_installed, or adb_market_search. No exclusions, prerequisites, or ordering guidance are given.

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