Skip to main content
Glama

version_current

Read-onlyIdempotent

Returns the current base version ID—adopted, reverted-to, or initial snapshot—so you can supply the parent for version creation, launches, and noise estimates.

Instructions

Return the id of the current base version: the latest adopted or reverted-to snapshot, or the initial snapshot before any adoption. Use it to get the parent for version_create, run_launch and noise_estimate; use ledger_history for the whole base chain. Read-only. Returns {"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": {
      "config": "<config>"
    },
    "name": "version_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesPath of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • addedInput schema / properties / config / description
      Added value: +"Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path."
  2. First observedv0.1.7

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the 'Read-only' sentence adds little beyond structured data. However the description supplies two things annotations cannot: the resolution semantics of 'current' (adopted/reverted-to vs. initial snapshot) and the concrete return payload {"version": "<sha256>"}, which matters because no output schema exists.

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?

Three compact sentences ordered by importance: what it returns, what to use it for, what it does not replace, then the return shape. No filler, and the scope-defining sentence is front-loaded. The only mild redundancy is 'Read-only', which restates the annotations.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the description covers resolution semantics, intended callers, the sibling alternative, and the return shape. An agent has everything needed to call it correctly and interpret the result.

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 the single `config` parameter is fully documented in the schema, including the workspace-selection behavior and the --config rejection rule. The description says nothing about `config`, so it adds no meaning beyond the schema; baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Return the id of the current base version') and then precisely defines what 'current' resolves to: the latest adopted or reverted-to snapshot, or the initial snapshot before any adoption. This distinguishes it clearly from ledger_history, which the description names as the tool for the whole chain.

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

Usage Guidelines5/5

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

Explicitly names downstream consumers ('use it to get the parent for version_create, run_launch and noise_estimate') and names the alternative for a different need ('use ledger_history for the whole base chain'). Both when-to-use and when-to-use-something-else are stated.

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