Skip to main content
Glama

sitekick_release_get

Read-onlyIdempotent

Read the immutable release and its manifest.

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

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's one contribution beyond that is the word 'immutable', signalling the release cannot be mutated, plus the fact that a manifest is returned alongside the record. It says nothing about behavior when the release is missing or about access scoping, which the annotations do not cover.

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 with zero filler. It is efficient, though its brevity borders on under-specification rather than tightness.

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?

Because an output schema exists, the return shape (release plus manifest) need not be spelled out. The remaining gap is the 0%-documented required parameters and the site scoping rule, which leaves the definition slightly thin for a nested-object input, but acceptable for a simple read.

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 description coverage is 0% for two required parameters, and the description names neither. It gives no hint that a release_id must be supplied inside a nested payload object, nor that a separate site_ref scopes the lookup, so the agent gets no meaning beyond the raw regex patterns in the schema.

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 ('Read') and resource ('the immutable release and its manifest'), which is more informative than a bare 'get release'. It does not, however, differentiate itself from nearby reads like sitekick_release_review_get or sitekick_release_preview, leaving the agent to infer from names 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?

There is no guidance on when to call this versus sibling reads such as sitekick_release_review_get or sitekick_release_preview, and no stated preconditions (e.g., that a release must already be prepared or activated). Usage is only implied by the verb 'Read'.

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