Skip to main content
Glama
openl-tablets

OpenL MCP Server

Official

Save Project to Git

openl_save_project

Save project changes to Git by providing a commit message. Use after editing to create a new revision and transition the project to OPENED; optionally close the project in the same request.

Instructions

Save project changes to Git. Works only when project status is EDITING (after opening and making changes). Requires comment (used as revision/commit message). Creates a new revision and transitions project to OPENED. Optional closeAfterSave: true saves and closes in one request. Use after update_table, append_table, or other edits. Does not work for repository 'local'. Validates project before saving if validation endpoint is available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentYesRequired. Comment for the new revision (commit message). Save only works when project status is EDITING; after save a new revision is created and project transitions to OPENED.
projectIdYesProject ID returned by backend. Use the exact 'projectId' value from openl_list_projects() response without modification or reformatting.
closeAfterSaveNoOptional. If true, close the project after saving (sends status CLOSED with comment in one request). Use when user asks to 'save and close'.
response_formatNoResponse format: 'json' for structured data, 'markdown' for human-readable (default), 'markdown_concise' for brief summary (1-2 paragraphs), 'markdown_detailed' for full details with contextmarkdown
Behavior4/5

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

Beyond the openWorldHint annotation, the description reveals key behaviors: creates a new revision, transitions project to OPENED, validates if endpoint available, and optional close behavior. No contradictory or hidden information.

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 five sentences, front-loaded with the main purpose, and each sentence adds essential information without redundancy. No wasted words.

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 4 parameters, the description covers prerequisites, behavior, and state transitions adequately. It omits return value details but that is acceptable as output schema is absent. The tool's complexity is moderate and description is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions. The description adds value by explaining the comment parameter's role as commit message and the closeAfterSave parameter's one-request behavior, going beyond the schema hints.

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 tool saves project changes to Git, with specific verb 'Save' and resource 'project changes'. It distinguishes from siblings like openl_close_project and openl_create_project by focusing on saving/committing. The precondition (EDITING status) and outcome (new revision, OPENED) are explicit.

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 states when to use: 'after update_table, append_table, or other edits', and when not: 'Does not work for repository local' and 'Works only when project status is EDITING'. It does not explicitly name alternatives but provides sufficient context given the sibling list.

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