Skip to main content
Glama

sitekick_release_review_get

Read-onlyIdempotent

Read review status by exact review ID and hash. If approved, retain the returned publication_request and use its exact operation, approval and idempotency identity.

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_ref": "<site_ref>",
      "payload": "<payload>"
    },
    "name": "sitekick_release_review_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.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety behavior is covered. The description adds genuinely new context about the approval hand-off and identity reuse for a later publication, but says nothing about the alternate listing payload or about failure behavior for a mismatched hash.

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?

Two compact sentences, front-loaded with the read operation and then the follow-up action. Nothing is redundant, though the second sentence packs several identity concepts without unpacking them.

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?

An output schema exists, so return shape need not be described. However, the schema exposes two mutually exclusive payload shapes and the description documents only one, leaving an agent unaware that a paginated job-scoped listing is possible.

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 0%, so the description must carry meaning. It explains the review_id/review_hash pairing as an exact-identity lookup, which the regex patterns alone would not convey as intent, but it completely ignores site_ref and the entire campaign_job_id/limit/offset payload branch.

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 and resource ('Read review status') plus the keying requirement ('by exact review ID and hash'), which distinguishes it from the mutation-oriented sibling sitekick_release_review. It does not name a sibling explicitly, so it stops short of a 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?

Provides forward guidance ('If approved, retain the returned publication_request and use its exact operation, approval and idempotency identity'), which tells the agent what to do after a successful read. It never states when to call this instead of sitekick_release_review or sitekick_release_get, and gives no exclusion criteria.

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