Skip to main content
Glama

sitekick_site_inspect

Read-onlyIdempotent

Inspect the selected site and its available authoring capabilities.

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": {
      "payload": "<payload>",
      "site_ref": "<site_ref>"
    },
    "name": "sitekick_site_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is carried by structured data. The description adds modest context by signaling that the result reports authoring capabilities (i.e., what the agent can do next on the site), but says nothing about authentication, site-selection state requirements, or whether inspection is cheap or expensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, so nothing is wasted, but the brevity comes at the cost of specification rather than from tight editing. It is short without being informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be documented, but the input side is under-served: a nested payload object, a patterned site reference, and a notion of "selected site" state are all left unexplained. For a tool whose only disambiguation from a large sibling set would come from the description, this leaves the agent guessing.

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?

Both parameters are required and schema description coverage is 0%; site_ref is only obliquely referenced by "the selected site," and the nested payload object with its native_source_page integer (0-199) is completely unexplained in the description or schema. With coverage this low, the description needed to compensate and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ("inspect") and a resource ("the selected site") plus a hint at scope ("available authoring capabilities"). However, "inspect" is broad and the sentence doesn't distinguish this from siblings that also surface site state, such as sitekick_site_existing_list or sitekick_workspace_read, so an agent cannot confidently choose between them from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"The selected site" weakly implies a prerequisite (a site must already be selected, presumably via sitekick_site_existing_select), but this is never stated. There is no explicit when-to-use guidance, no when-not-to-use, and no named alternative for the many sibling tools in this namespace.

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