Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

get_version

Read-only

Reads ONE version of the history: its counts and the inventory of its blocks, or its complete SchemaData (include:'full'). Precedes restore_version: list_versions returns only a label and two counts, which is not enough to know what you would go back to — and a restore REPLACES the whole schema. READ-ONLY.

Input Schema

NameRequiredDescriptionDefault
includeNo'summary' (default): counts and inventory of the blocks (id, name, type). 'full': the complete SchemaData of the snapshot — LARGE, request it only to inspect a precise detail before restoring.
versionYesThe number returned by list_versions.
expectedProjectIdNoUUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / expectedProjectId / description
      Previous value: -"UUID du projet visé par CET appel. Cible RÉELLEMENT ce projet au lieu du projet de session. Refusé sans rien modifier si l'accès n'est pas accordé."New value: +"UUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted."
    • changedInput schema / properties / include / description
      Previous value: -"'summary' (défaut) : décomptes et inventaire des blocs (id, nom, type). 'full' : le SchemaData complet de l'instantané — VOLUMINEUX, ne le demande que pour inspecter un détail précis avant de restaurer."New value: +"'summary' (default): counts and inventory of the blocks (id, name, type). 'full': the complete SchemaData of the snapshot — LARGE, request it only to inspect a precise detail before restoring."
    • changedInput schema / properties / version / description
      Previous value: -"Le numéro rendu par list_versions."New value: +"The number returned by list_versions."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the 'READ-ONLY' line is partly redundant, but the description adds real behavioral context: that restore REPLACES the whole schema (motive for inspecting first) and that 'full' returns LARGE payloads. It does not mention error behavior or rate/cost implications beyond size.

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 dense sentences, front-loaded with the core action, then the sibling distinction, then the safety note. No filler and no repetition of the schema.

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 read-only, no-output-schema tool with fully documented parameters, the description covers purpose, alternatives, and the return-shape distinction between summary and full. Only minor gaps (e.g., what happens with an invalid version number) remain.

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 include, version, and expectedProjectId in full; the description only restates the include:'full' tradeoff. Per the baseline rule, 3 is appropriate when the schema carries the parameter semantics.

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 ('Reads ONE version of the history') and enumerates what is returned (counts, block inventory, or full SchemaData). It explicitly distances itself from both list_versions and restore_version, so an agent can route correctly without opening a schema.

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?

Names the sibling alternative (list_versions) and explains why it is insufficient ('only a label and two counts'), then positions this tool as the prerequisite step before restore_version. The when-to-use condition and the downstream workflow are both explicit.

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

All OrgGen AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources