Skip to main content
Glama

get_version

Read-onlyIdempotent

Retrieve a recorded version of an agent, schema, trigger, or MCP server by resource ID and version number to inspect it before restoring.

Instructions

Retrieve one recorded resource version for inspection before restoring it.

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": {
      "resource_type": "<resource_type>",
      "resource_id": "<resource_id>",
      "version": "<version>"
    },
    "name": "get_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesVersion number
resource_idYesResource UUID
resource_typeYesResource type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.4
    • changedInput schema / properties / resource_id / description
      Previous value: -"UUID do recurso"New value: +"Resource UUID"
    • changedInput schema / properties / resource_type / description
      Previous value: -"Tipo do recurso"New value: +"Resource type"
    • changedInput schema / properties / version / description
      Previous value: -"Número da versão"New value: +"Version number"
  2. First observedv0.1.0

TDQS

A3.5/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=false, so the safety profile is fully covered. The description adds only that the version is "recorded" (a historical snapshot) and intended for inspection, which is modest added context beyond the annotations.

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?

A single front-loaded sentence with no filler; the verb and resource come first and the purpose clause follows. Nothing is wasted.

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?

All required parameters are documented and annotations cover the safety profile, but with no output schema the description never indicates what a retrieved version contains (metadata vs. full resource payload). For a read tool whose return shape is undefined, that is a noticeable gap.

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 100% and all three parameters (resource_type enum, resource_id UUID, version integer) are documented in the schema. The description adds no format or selection detail beyond that, so the 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?

States a specific verb ("Retrieve") and resource ("one recorded resource version") with clear scope of a single item. The phrase "before restoring it" implicitly separates it from rollback_version, though it 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?

"for inspection before restoring it" gives a clear usage context, implying this is the read step preceding a rollback. It does not explicitly name rollback_version as the alternative or state when not to use this tool, so guidance is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools