NomaCMS MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Get Entry Version

get_entry_version

Retrieve a specific version's metadata and raw snapshot payload for an entry. Use to access saved field values in restoration format.

Instructions

Fetch a single version's metadata and raw snapshot payload. The snapshot contains the saved field values in restoration format; for API-rendered content use get_entry with state='published'.

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": {
      "collection_slug": "<collection_slug>",
      "uuid": "<uuid>",
      "version_number": "<version_number>"
    },
    "name": "get_entry_version"
  }
}

Input Schema

Name	Required	Description
`uuid`	Yes	The entry UUID
`version_number`	Yes	The version number (1-based)
`collection_slug`	Yes	The collection slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations exist, so description carries full burden. It discloses snapshot format as 'restoration format' but does not mention permissions, error handling, rate limits, or if the operation is read-only. Adequate for a simple fetch, but lacks detail on behaviors beyond what is stated.

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?

Two concise sentences, front-loaded with the primary purpose. Every sentence adds value with no redundancy, achieving high information density.

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?

Given no output schema and no annotations, the description explains the snapshot format and contrasts with get_entry. It covers the core functionality well, but could mention that version_number must be valid and the return type. Still, it is fairly complete for a straightforward read tool.

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 coverage is 100% with descriptions for all three parameters. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 the verb 'Fetch' and the resources 'single version's metadata and raw snapshot payload'. It distinguishes from sibling tool 'get_entry' by specifying alternative for rendered content, making the purpose unambiguous.

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?

Provides explicit guidance on when to use (fetching version metadata and snapshot) and when not to (for rendered content, use get_entry with state='published'). Names the alternative tool, giving clear usage boundaries.

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