Skip to main content
Glama

List sites

fleet__list_sites
Read-onlyIdempotent

Enumerate connected sites in the current agency, optionally filtered. Each site names the client it belongs to, when the agency set one, and the services that reach it, such as the Cloudflare zone it is on: use that service’s tools for the site. A live site with a staging copy carries staging_site_id; the copy carries live_site_id.

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

Input Schema

NameRequiredDescriptionDefault
filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds context those annotations cannot: what each returned site contains (client attribution, discovery time, reaching services such as the Cloudflare zone) and the staging/live cross-reference via staging_site_id and live_site_id. Missing are pagination/result-size behavior and whether results are permission-scoped.

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 sentences with the purpose front-loaded and no filler. The middle sentence is slightly tangled ('names the client it belongs to, when the agency set one, and the services that reach it'), but every clause carries information about the response shape.

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?

There is no output schema, so the description carries the burden of explaining returns, and it does so well for this read-only lister: per-site fields, service associations, and the staging/live pairing. Only pagination and the default unfiltered-result scope are left unspecified.

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?

The only parameter is a nested filter object, and the description says merely 'optionally filtered' without expanding on tags, status, tag_match, plugin_slug or selection_id. The schema itself documents each of those fields, so the baseline of 3 applies; the description adds no filter semantics beyond the structured 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?

Names a specific verb and resource with scope: 'Enumerate connected sites in the current agency, optionally filtered.' That is unambiguous and distinct from mutation siblings like fleet__bulk_edit or fleet__run_across_sites. It does not explicitly differentiate itself from near-neighbors such as fleet__list_site_groups or recipe__fleet_inventory, which would have taken it to a 5.

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 implied rather than stated: the description tells the agent that per-service attributes exist and to 'use that service's tools for the site,' which is useful follow-up routing. It never states when to call this versus list_site_groups or fleet_inventory, nor any prerequisite or exclusions for the filter argument.

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