Skip to main content
Glama

Websites auflisten

website_list
Read-only

Zeigt alle Websites dieses Kontos mit Plan, Adresse und ob sie veröffentlicht werden können.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavioral context by disclosing the returned content (plan, address, publishability), but it says nothing about result volume, ordering, or whether unpublished sites are included.

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 that delivers scope and returned fields with no filler. It could be marginally sharper by stating the unfiltered, account-wide nature more explicitly, but nothing is wasted.

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 read-only list tool with no output schema, the description conveys enough: what it lists, for which account, and which fields come back. Only minor gaps remain (pagination, ordering, inclusion of non-published sites) for an agent to call it confidently.

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, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies an unparameterized account-wide listing with no filtering options.

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 ("Zeigt") and a clearly scoped resource ("alle Websites dieses Kontos"), and names the fields returned (Plan, Adresse, Veröffentlichkeitsfähigkeit). This clearly separates it from creation/mutation siblings like website_anlegen or website_einstellungen, though no sibling is named explicitly.

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 account-wide listing scope implies the usage context, but there is no explicit statement of when to prefer this tool over alternatives (e.g. fs_list or check_site for per-site checks) and no prerequisites or exclusions mentioned. Usage is inferable rather than guided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources