Skip to main content
Glama

SoFast

Get site status

get_site_status
Read-only

Shows one site: its address, whether it is online, its file count, and the outcome of its latest publish, including the reason a publish failed.

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

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its numeric id, its address (name.sofast.website or a custom domain) or its URL.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/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's contribution is the field inventory, notably that a failed publish's reason is included, but it says nothing about behavior on invalid site references or how much data a large site returns.

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 sentence, front-loaded with the scope ("one site") and then the returned fields. No filler, though most of its length is a field list rather than routing guidance.

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, the description usefully sketches the return contents, which is the main thing an agent needs. Missing pieces are modest: not-found behavior and any indication of how recent the online/publish data is.

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 coverage is 100% and the schema already explains the three accepted identifier forms (numeric id, address, URL). The description adds no syntax, normalization, or precedence rules beyond what the schema states, so baseline 3 applies.

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?

"Shows one site" gives a specific verb and cardinality, and the enumeration of address, online state, file count, and latest publish outcome makes the resource concrete. It implicitly contrasts with list_sites (one vs many) but never names that sibling.

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: fetch details for a single already-identified site. There is no statement of when to prefer this over list_sites, nor any note about what to do when the site does not exist.

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