Skip to main content
Glama

Press5 launch pad

List my sites

list_sites
Read-only

List the sites on this Press5 account, with their URLs and status, plus the account limits.

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
tokenNoA press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is disclosing the payload shape (sites with URLs and status, plus account limits). It says nothing about ordering, pagination, or what happens with a large number of sites, and does not repeat the token/auth condition that matters right after login_check.

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 sentence, front-loaded with the verb and resource, and every clause carries content. The trailing 'plus the account limits' is slightly loose about what those limits are, 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-required-parameter read tool with full schema coverage, no output schema, and a readOnlyHint annotation, this is close to sufficient; stating the returned fields compensates for the missing output schema. The only real gap is the absence of guidance on where this fits relative to site_info and the mutating siblings.

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% and the single token parameter is fully explained there, including the 'only needed when the MCP connection has no Authorization header' condition. The description adds no meaning beyond that, so the baseline 3 applies rather than a higher score.

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?

The description names a specific verb and resource ('List the sites on this Press5 account') and goes further to say what comes back: URLs, status, and account limits. That distinguishes it from a single-site lookup like site_info, though it never names a sibling 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 only implied: an agent can infer this is the entry-point inventory call before site_info or delete_site/deploy_site. There is no explicit when-to-use, no exclusion of alternatives, and no statement of prerequisites beyond the token note living in the schema.

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