Skip to main content
Glama

SoFast

List sites

list_sites
Read-only

Lists the sites on the connected Sofast account, with their address, status and last publish, and whether a new site can be created.

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_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

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 and openWorldHint=false, so the safety profile is covered. The description adds useful disclosure of the payload contents and a capability flag about new-site creation, but says nothing about result size, pagination, or behavior when the account has no sites.

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 well-formed sentence that front-loads the action and resource, then lists return contents compactly. No filler, though the trailing clause about creating a new site could be phrased more crisply.

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?

With no output schema and no parameters, the description carries responsibility for describing results, and it names the returned fields. Minor gap: no indication of pagination or ordering for accounts with many sites.

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 no parameters, so the schema's only role is confirming the empty object; the baseline for a 0-parameter tool is 4. The description correctly frames the call as unfiltered account-wide enumeration.

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 ('Lists') and resource ('sites on the connected Sofast account') and enumerates the data returned: address, status, last publish, and whether a new site can be created. An agent can tell this is the enumeration entry point versus the mutation siblings (create_site, delete_site, rename_site), though it doesn't name an alternative 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?

Usage is implied rather than stated: as a zero-parameter read of all sites, it is clearly the discovery/orientation call, and the mention of 'whether a new site can be created' hints at routing to create_site. No explicit when-to-use vs when-not, and no prerequisites are given.

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