MCPDactyl

Test panel credentials

panel_test

Verifies which API keys are valid for a panel by sending a lightweight request to each API.

Instructions

Check which API keys work for a panel by making a lightweight request to each API.

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

Input Schema

Name	Required	Description	Default
`name`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations exist, so the description carries the whole burden. It usefully discloses that real network requests are made ('lightweight request to each API'), which signals cost and non-destructiveness, but says nothing about what happens on partial failure, whether it reports per-key results, whether it is rate-limited, or what output it returns.

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?

One front-loaded sentence with no filler and the mechanism stated immediately. Slightly ambiguous wording ('each API' when there is one panel parameter) costs it the top mark.

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 simple one-optional-param diagnostic tool with no output schema, the description is close but not sufficient: the role of 'name', the behavior when it is omitted, and the shape of the diagnostic result are all unstated, and with no output schema the description is the only place result semantics could be conveyed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'name' parameter, and the description never mentions it at all. It is unclear whether 'name' selects one panel, whether omitting this optional parameter tests every configured panel, or what the string refers to — the description does not compensate for the total coverage gap.

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 (check/test), a specific resource (API keys for a panel) and the mechanism (lightweight request to each API). This is enough to distinguish it from the sibling set (panel_add, panel_use, panel_list), though the description never names those siblings explicitly and the term 'API keys' differs slightly from the title's 'credentials'.

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 a verification step, presumably before or after panel_add/panel_use, but the description never says when to prefer it, that it should follow panel_add, or that panel_list is a different (non-verifying) operation.

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

Deploy Server