Skip to main content
Glama
Sign In
android-apk-orchestrator

android-apk-orchestrator

by HaizhuAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apk_list_agents

List the seven specialist agents for Android APK analysis, including their source skills and availability status.

Instructions

List the seven specialist agents, source skills, and availability.

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": "apk_list_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state the action and output content, but it does not explicitly address side effects, whether the operation is read-only, or edge behavior such as whether unavailable agents are omitted or listed as unavailable. The 'List' verb implies safety, but only implicitly.

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?

The description is a single front-loaded sentence with no filler. Every word conveys needed information: the action, the target entities, and the specific fields returned.

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 zero-parameter, output-schema-bearing listing tool, the description is largely complete: it names the exact content of the response. The only gap is the absence of explicit guidance about when to use this tool in a workflow, which is a minor omission given the low complexity.

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 has zero parameters and the input schema is empty with 100% schema description coverage. There is nothing for the description to add about parameters, so the baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'List the seven specialist agents' and names the returned content ('source skills, and availability'). This clearly distinguishes it from sibling tools like apk_dispatch or apk_report, which perform different actions.

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 intended use is implied by the verb 'List' and by being the only listing tool among its siblings, but the description does not explicitly state when to use it versus alternatives or how it relates to preceding actions like apk_dispatch. There is no exclusions or conditional guidance.

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