Skip to main content
Glama

show_versions

Retrieve version metadata for a model, including Current and Forecast. Version IDs are needed for set_versionswitchover.

Instructions

List version metadata (Current, Forecast, etc.) for a model. Version IDs are needed for set_versionswitchover. Note: requires model ID (name resolution not supported).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelIdYesAnaplan model ID (name resolution not supported -- use show_models to find the ID)
limitNoMax items to return (default 50, max 1000)
searchNoFilter by name or ID (case-insensitive substring match)

Implementation Reference

  • The 'show_versions' tool handler: registers the tool with server.tool(), defines the schema (modelId string + paginationParams), and implements the handler that calls apis.versions.list(modelId) and formats results as a table with Name, Current, Actual, and ID columns.
    server.tool("show_versions", "List version metadata (Current, Forecast, etc.) for a model. Version IDs are needed for set_versionswitchover. Note: requires model ID (name resolution not supported).", {
      modelId: z.string().describe("Anaplan model ID (name resolution not supported -- use show_models to find the ID)"),
      ...paginationParams,
    }, async ({ modelId, limit, search }) => {
      const versions = await apis.versions.list(modelId);
      return tableResult(versions, [
        { header: "Name", key: "name" },
        { header: "Current", key: "isCurrent" },
        { header: "Actual", key: "isActual" },
        { header: "ID", key: "id" },
      ], "versions", { limit, search });
    });
  • The input schema for 'show_versions' includes modelId (required string with description about name resolution not supported) and paginationParams (optional limit and search). Output is formatted as a text table.
    server.tool("show_versions", "List version metadata (Current, Forecast, etc.) for a model. Version IDs are needed for set_versionswitchover. Note: requires model ID (name resolution not supported).", {
      modelId: z.string().describe("Anaplan model ID (name resolution not supported -- use show_models to find the ID)"),
      ...paginationParams,
    }, async ({ modelId, limit, search }) => {
      const versions = await apis.versions.list(modelId);
      return tableResult(versions, [
        { header: "Name", key: "name" },
        { header: "Current", key: "isCurrent" },
        { header: "Actual", key: "isActual" },
        { header: "ID", key: "id" },
      ], "versions", { limit, search });
    });
  • The tool is registered via server.tool('show_versions', ...) inside the registerExplorationTools function in src/tools/exploration.ts.
    server.tool("show_versions", "List version metadata (Current, Forecast, etc.) for a model. Version IDs are needed for set_versionswitchover. Note: requires model ID (name resolution not supported).", {
      modelId: z.string().describe("Anaplan model ID (name resolution not supported -- use show_models to find the ID)"),
      ...paginationParams,
    }, async ({ modelId, limit, search }) => {
      const versions = await apis.versions.list(modelId);
      return tableResult(versions, [
        { header: "Name", key: "name" },
        { header: "Current", key: "isCurrent" },
        { header: "Actual", key: "isActual" },
        { header: "ID", key: "id" },
      ], "versions", { limit, search });
    });
  • The VersionsApi.list() method that performs the HTTP GET request to /models/{modelId}/versions and returns the versions list.
    async list(modelId: string) {
      const res = await this.client.get<any>(`/models/${modelId}/versions`);
      return res.versions ?? res.versionMetadata ?? [];
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only listing operation but does not detail pagination behavior, error handling (e.g., if model not found), or rate limits. The limit parameter description in the schema partially compensates, but the tool description itself lacks depth.

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 extremely concise with only two sentences. It front-loads the core purpose and then adds an important usage note. Every sentence provides value without any redundant or unnecessary text.

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?

For a simple listing tool with three parameters and no output schema, the description covers the essential: what it does, why to use it (for set_versionswitchover), and a key constraint (requires model ID). It lacks details on return structure or pagination, but given the tool's simplicity, it is mostly complete.

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%, so the schema already documents all three parameters. The description adds minimal extra information beyond what is in the schema, such as the note about model ID requirement which is also in the schema. Thus, the description does not significantly enhance parameter understanding.

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?

The description clearly states that the tool lists version metadata such as Current and Forecast for a model. It specifies the verb 'List' and the resource 'version metadata', and distinguishes itself from sibling 'show_*' tools by focusing on versions. The mention that version IDs are needed for set_versionswitchover adds context.

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

Usage Guidelines4/5

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

The description explicitly notes that a model ID is required and that name resolution is not supported, guiding users to first use show_models. It also states that version IDs output are used for set_versionswitchover, indicating a specific use case. However, it does not provide explicit when-not-to-use or alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/larasrinath/anaplan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server