Skip to main content
Glama

Freeze a snapshot

snapshot_temp

Create a fixed snapshot URL for the current Version while the canonical URL continues to track the latest Version.

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": {
      "temp_id": "<temp_id>"
    },
    "name": "snapshot_temp"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
temp_idYesThe Temp ID.
update_tokenNoScoped Temp update token. May be omitted when the MCP Authorization header contains an account API key that owns the Temp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The description adds useful state behavior: the snapshot URL is fixed while the canonical URL continues tracking the latest Version. Annotations already cover non-destructiveness and non-idempotency, so the added value is moderate; auth requirements and side effects are not disclosed.

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

Conciseness5/5

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

The description is a single, well-structured sentence with no filler. The core purpose is front-loaded, and the fixed-snapshot versus canonical-latest contrast is expressed economically.

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?

With no output schema, the description still does not explain what response to expect, how to access the created snapshot URL, or what 'Version' refers to relative to temp_id. Given openWorldHint=true, an agent needs more context to invoke the tool confidently.

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?

The input schema documents temp_id and update_token, but label is left undescribed, and the tool description adds no parameter-level meaning. It introduces the 'Version' concept but does not connect it explicitly to temp_id or explain how label and update_token should be used.

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 names a specific action ('Create a fixed snapshot URL'), a resource ('the current Version'), and a distinguishing behavioral contrast ('canonical URL continues to track the latest Version'). It clearly goes beyond restating the title, but it does not explicitly differentiate against sibling tools like publish_temp or update_temp.

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 description provides no guidance about when to use this tool versus the listed siblings, nor when not to use it. There is no mention of prerequisites, triggering conditions, or alternatives.

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.