Skip to main content
Glama

Press5 launch pad

Site details

site_info
Read-only

One site with its recent deploys (ids for rollback_site).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "site_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
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

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already covers the safety profile, and the description adds genuinely useful forward-looking context: the deploy ids returned feed rollback_site. It does not say how many deploys 'recent' means, what happens if the site does not exist, or that the token field is the fallback auth path.

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 fragment with no filler; the rollback cross-reference is packed into a parenthetical rather than a separate clause. It is terse to the point of trimming meaning, but nothing is wasted.

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 two-parameter read tool with no output schema, the description sketches the return shape (site + recent deploys) and the downstream use of the ids. The unresolved gaps — the format of the site identifier and the meaning of 'recent' — are enough that an agent could still call it incorrectly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: token is well documented in the schema, but the required 'site' parameter has no description there and the prose does not add one — it never states whether site is an id, slug, or domain. With a required identifier undocumented in both places, the description fails to compensate for the coverage gap.

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 identifies a specific resource ('One site') plus its payload ('recent deploys') and cross-references the rollback_site sibling, so it is distinguishable from list_sites. The verb is only implied ('one site with...'), which keeps it short of a full 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 by the parenthetical '(ids for rollback_site)', which tells the agent this is the tool to call before a rollback. There is no explicit when-to-use or when-not statement, and list_sites is not named as the alternative for the multi-site case.

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