Skip to main content
Glama
Sign In
mcp-server-sigma

mcp-server-sigma

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Workbooks Get Workbook Version History

workbooks_get_workbook_version_history
Read-only

Get version history for a workbook.

Instructions

Get version history for a workbook.

Follows Sigma's pagination to the last page and returns the keys of Sigma's page: entries from every page, total when Sigma sends it (Sigma's value), and nextPage null (hasMore false where Sigma sends it) since every page is read.

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": {
      "workbook_id": "<workbook_id>"
    },
    "name": "workbooks_get_workbook_version_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
workbook_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.4

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds meaningful behavior beyond that: it auto-follows Sigma pagination to the last page and explains the synthesized return shape, including entries, total, nextPage=null, and hasMore=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and the pagination/return-key details are relevant to correct invocation. The second sentence is dense but earns its place by preventing manual pagination assumptions.

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 a read-only, single-parameter tool with annotations and an output schema, the description is largely complete: it covers auto-pagination and return semantics. The main remaining gap is that workbook_id semantics are left to the schema, which has no description.

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 0%, so the description must carry the burden for workbook_id. It implies the parameter is tied to a workbook but does not explain identifier format, source, or constraints; for a single self-explanatory parameter this is minimally adequate rather than fully compensating.

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 starts with a specific verb-resource pair: 'Get version history for a workbook.' It is clearly distinguishable from the sibling report variant, workbooks_get_report_version_history, because it explicitly scopes the operation to a workbook.

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

Usage Guidelines2/5

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

The description explains pagination behavior but gives no guidance on when to use this tool versus alternatives, prerequisites, or conditions for choosing it over related version-history tools. Usage is only implied by the purpose.

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