Skip to main content
Glama
Sign In
mcp-1panel-plus

mcp-1panel-plus

by EC061
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Websites

list_websites
Read-only

Retrieve websites on a selected node with an optional domain/alias filter to review site entries while excluding internal filesystem paths.

Instructions

List websites on the selected node with optional name filter. Internal filesystem paths are excluded.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional domain/alias substring filter.
pageNo1-indexed page number.
nodeIdNoTarget node ID: "local" for the Main Node, or a numeric string ID (e.g. "3") from list_nodes.local
page_sizeNoItems per page (1-500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and open-world, so safety is covered; the description adds a non-obvious result-shaping fact that internal filesystem paths are excluded from the output. It does not discuss ordering, total counts, or pagination behavior, which is the remaining gap.

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?

Two short sentences with no filler; the core action and scope are front-loaded and the exclusion caveat follows immediately. Nothing could be removed without losing information.

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 read-only list tool with zero required parameters and a fully documented schema, the description is serviceable, but with no output schema it never hints at what a result entry looks like (website name, domains, status) or how paging interacts with large node inventories.

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% (name substring filter, 1-indexed page, page_size 1-500, nodeId with local/numeric pattern), so the schema already carries full parameter meaning. The description restates only the optional name filter and node selection, adding no format or constraint detail beyond the 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 and resource ("List websites") plus its scope ("on the selected node") and an optional filter, which separates it from get_website and the domain/proxy listers. It stops short of naming any sibling explicitly, so differentiation is inferred from the singular/plural scope rather than stated.

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 node scoping implies the tool is used when you already have a node context, and the param schema points at list_nodes, but the description itself gives no when-to-use guidance, no exclusions, and no direction toward get_website or list_website_domains for other needs.

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