Skip to main content
Glama
Pickle Air MCP

Pickle Air MCP

pickle_doctor

Read-onlyIdempotent

Diagnose local loopback ADB connectivity and existing Swift permissions without changing settings; use it as a setup check, not a complete end-to-end test.

Instructions

Diagnose the local loopback ADB connection and existing Swift/permissions. Changes no settings. Not a complete end-to-end test.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds a useful limitation ('Not a complete end-to-end test') but 'Changes no settings' largely restates the annotations and no return or failure behavior is described.

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 diagnostic scope, with no obvious filler. 'Swift/permissions' is terse enough to be slightly ambiguous, but the overall structure is efficient.

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?

For a zero-parameter diagnostic with rich annotations but no output schema, the description covers scope and a key limitation. It does not explain what findings or failure modes the agent should expect, which matters for a diagnostic tool whose output is undocumented.

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?

There are zero parameters, so baseline 4 applies. The description correctly introduces no parameter semantics that could conflict with the empty schema.

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 (diagnose) and concrete targets (local loopback ADB connection, Swift/permissions). It is distinguishable from the named siblings, which are ask/call/download/read/usage operations, though 'Swift/permissions' remains somewhat cryptic.

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 phrase 'Not a complete end-to-end test' establishes an important usage boundary, but there is no explicit guidance on when to prefer this over siblings such as pickle_call or pickle_read. Usage is implied for connection troubleshooting only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.