Skip to main content
Glama
openl-tablets

OpenL MCP Server

Official

openl Close Project

openl_close_project
Destructive

Close a project, either saving changes with a comment or discarding after user confirmation, to prevent accidental data loss.

Instructions

Close a project. If the project has unsaved changes (status EDITING), you must either save (saveChanges: true with comment) or discard (discardChanges: true). When discarding, ask the user for confirmation and then call again with confirmDiscard: true. Prevents accidental data loss.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID returned by backend. Use the exact 'projectId' value from openl_list_projects() response without modification or reformatting.
saveChangesNoIf true, save changes before closing (requires comment). If false or omitted and project has unsaved changes, will error unless discardChanges is true.
commentNoGit commit comment. Required if saveChanges is true. Optional if saveChanges is false or omitted.
discardChangesNoIf true, close without saving (unsaved changes will be lost). When project is EDITING, you must also set confirmDiscard: true to confirm.
confirmDiscardNoWhen closing with discardChanges: true and project has unsaved changes, must be set to true (explicitly) to confirm. Omitted or false will return a confirmation prompt. Ask the user first, then call again with confirmDiscard: true.
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
Behavior5/5

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

Description adds significant behavioral context beyond annotations: explains the EDITING status flow, the need for user confirmation on discards, and the two-step process for discarding. This complements the destructiveHint annotation.

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?

Description is concise (3 sentences) and front-loaded with the main action. Each sentence adds value, though the second sentence could be slightly clearer. Overall efficient.

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 6 parameters (1 required) and no output schema, the description adequately explains the close workflow. It does not detail the response_format parameter but the schema suffices. Missing explicit return value info but acceptable for a mutating action.

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 covers all parameters with descriptions (100% coverage). The description adds meaning by explaining the logical flow (save vs discard, confirmDiscard requirement) and the condition of EDITING status, enhancing understanding beyond raw schema.

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?

Purpose is clearly stated: 'Close a project.' The verb 'close' is specific, and the resource 'project' is explicit. Among siblings, this tool uniquely handles closing, distinguishing it from open, save, deploy, etc.

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 explicit guidance on handling unsaved changes: either save with comment or discard with user confirmation. Mentions preventing accidental data loss. Lacks explicit when-not-to-use or alternatives, but context is sufficient.

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