Skip to main content
Glama
openl-tablets

OpenL MCP Server

Official
by openl-tablets
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Get Project Revision History

openl_repository_project_revisions
Read-onlyIdempotent

Retrieve commit history for a project using its stable ID, including hashes, authors, timestamps, and commit types. Supports search, pagination, and technical-revision filters.

Instructions

Get revision history (commit history) of a project in the branch it is currently on. Addressing the project by its stable ID keeps history available after an unsaved rename. Returns revisions with commit hashes, authors, timestamps, and commit types, with pagination and optional search and technical-revision filters. Use the projectId returned by openl_list_projects; do not construct it from the displayed project name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (0-based). Mutually exclusive with offset; the backend defaults to 0 when both are omitted.
sizeNoPage size (default: 50, max: 200)
offsetNoItem offset (0-based). Mutually exclusive with page.
searchNoSearch term to filter revisions by commit message or author
techRevsNoInclude technical revisions (default: false)
projectIdYesProject ID returned by backend. Use the exact 'projectId' value from openl_list_projects() response without modification or reformatting.
response_formatNoResponse format: 'json' for structured, round-trippable data (default), 'markdown' for human-readable output, 'markdown_concise' for a brief summary (1-2 paragraphs), or 'markdown_detailed' for full details with contextjson

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv1.2.0
    • removedInput schema / properties / branch
      Removed value: -{
-  "description": "Branch name (optional, only if repository supports branches)",
-  "type": "string"
-}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Item offset (0-based). Mutually exclusive with page.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / page / description
      Previous value: -"Page number (0-based, default: 0)"New value: +"Page number (0-based). Mutually exclusive with offset; the backend defaults to 0 when both are omitted."
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Project ID returned by backend. Use the exact 'projectId' value from openl_list_projects() response without modification or reformatting.",
+  "type": "string"
+}
    • removedInput schema / properties / projectName
      Removed value: -{
-  "description": "Project name within the repository (e.g., 'InsuranceRules', 'AutoPremium', 'ClaimProcessing')",
-  "type": "string"
-}
    • removedInput schema / properties / repository
      Removed value: -{
-  "description": "Repository identifier. Pass either the 'id' or the 'name' field from openl_list_repositories() — the tool accepts both (and is case-insensitive). DO NOT invent values like 'Design Repository' or 'design-repo'; the actual names are typically short tokens (e.g. 'Design'). Always call openl_list_repositories() first if you don't already have the value in context.",
-  "type": "string"
-}
    • changedInput schema / properties / response_format / default
      Previous value: -"markdown"New value: +"json"
    • changedInput schema / properties / response_format / description
      Previous value: -"Response format: 'json' for structured data, 'markdown' for human-readable (default), 'markdown_concise' for brief summary (1-2 paragraphs), 'markdown_detailed' for full details with context"New value: +"Response format: 'json' for structured, round-trippable data (default), 'markdown' for human-readable output, 'markdown_concise' for a brief summary (1-2 paragraphs), or 'markdown_detailed' for full details with context"
    • addedInput schema / properties / size / default
      Added value: +50
    • addedInput schema / properties / techRevs / default
      Added value: +false
    • changedInput schema / required
      Previous value: -[
-  "repository",
-  "projectName"
-]New value: +[
+  "projectId"
+]
  2. Changed1 schema field changedv1.1.0
    • changedInput schema / properties / repository / description
      Previous value: -"Repository name (display name, not ID). Use the 'name' field from openl_list_repositories() response (e.g., if list_repositories returns {id: 'design-repo', name: 'Design Repository'}, use 'Design Repository' here, NOT 'design-repo')."New value: +"Repository identifier. Pass either the 'id' or the 'name' field from openl_list_repositories() — the tool accepts both (and is case-insensitive). DO NOT invent values like 'Design Repository' or 'design-repo'; the actual names are typically short tokens (e.g. 'Design'). Always call openl_list_repositories() first if you don't already have the value in context."
  3. First observedv0.0.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond that: history remains available after an unsaved rename and the response includes commit hashes, authors, timestamps, commit types, pagination, and filters. No rate-limit or auth details are given, but the annotation coverage makes this acceptable.

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?

Four sentences, each carrying distinct information: scope, stable-ID rationale, return contents, and identifier provenance. The description is front-loaded with the action and resource, though the third sentence is slightly list-heavy with multiple return fields and filter concepts.

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?

There is no output schema, so the description appropriately states the returned revision fields and available filters. Combined with high schema coverage and read-only/idempotent annotations, this gives an agent enough to invoke the tool correctly, though the exact paginated response shape is not described.

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 every parameter, including the projectId provenance rule. The description reinforces the projectId guidance and summarizes pagination, search, and technical-revision filters, but it does not add parameter-level detail beyond what the schema provides. The baseline 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?

Opens with an explicit verb and resource combination: 'Get revision history (commit history)' scoped to the branch the project is currently on. This is clearly distinguishable from sibling tools like branch listing or local-change tools, so an agent can identify it as the commit-history read without ambiguity.

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?

Provides concrete selection and invocation guidance: use the projectId returned by openl_list_projects and do not construct it from the displayed project name. It also clarifies that the history is branch-scoped and lists available filters, though it does not explicitly mention when not to use this tool or name a sibling alternative.

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/openl-tablets/openl-mcp'

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