Skip to main content
Glama

adb_plugin_info

Displays plugin system information, including the plugin directory, creation steps, and loaded plugin count.

Instructions

Show information about the plugin system: directory, how to create plugins, and loaded plugin count.

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

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.5/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden. "Show information" does signal a non-mutating read, and the description discloses the three categories of content returned, which is useful behavioral context. It stops short of confirming purely read-only semantics, whether anything can be altered, or how the creation guidance is sourced, leaving gaps that a zero-annotation tool would ideally close.

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?

A single front-loaded sentence with the resource first and the returned items as a compact list; nothing is padded or repeated. Minor awkwardness comes from bundling "how to create plugins" into a list of return values, which reads more like documentation than data, but the sentence still earns its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description is the only source of information, and for a zero-argument informational tool it covers what matters by listing the three payload sections. It is incomplete in one practical respect: the sibling adb_plugin_list exists and the description never clarifies the boundary between counting loaded plugins and listing them.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema is empty and fully described, and the description correctly sets expectations that all output comes from a fixed, argument-free introspection call.

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 ("Show information") and a specific resource ("the plugin system"), then enumerates the exact payload: directory, plugin-creation guidance, and loaded plugin count. That is far more precise than a bare name restatement. It does not, however, distinguish itself from the sibling adb_plugin_list, so an agent must guess which of the two to call for plugin enumeration.

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?

The enumerated contents imply the usage context (a discovery/help call you make when you need to know where plugins live or how to author one), but there is no explicit when-to-use statement and no mention of when to prefer adb_plugin_list. The strongest guidance present is indirect, coming from what the tool returns rather than from an instruction.

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