Skip to main content
Glama
Sign In

Meridian

by ai.the-meridian
OverviewDiscussions(2)Admin

Create Deployment

deployment_create
Idempotent

Triggers a manual deployment of git_sha to one of an app's environments, exactly like the Deploy button in the Meridian web app. Takes the app_id returned by apps_list, the environment_id returned by environments_list (production, or a development or staging environment when the app has one), and the git_sha to deploy (optional git_ref for display only).

IDEMPOTENT: calling this again with the same environment_id and git_sha while that exact deployment is still in flight (queued/building/deploying/verifying) returns the SAME deployment (created: false) instead of creating a duplicate. Calling it with a DIFFERENT git_sha while a deployment is active for that environment is refused. Meridian allows only one active deployment per environment. Use deployment_get to poll the resulting deployment_id for status, and deployments_list/logs_tail for history and live logs.

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": {
      "app_id": "<app_id>",
      "environment_id": "<environment_id>",
      "git_sha": "<git_sha>"
    },
    "name": "deployment_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app uuid returned by `apps_list`.
git_refNoOptional git ref (branch or tag) recorded alongside git_sha, for display only.
git_shaYesThe exact commit SHA to build and deploy.
environment_idYesThe uuid of the environment to deploy to, from `environments_list`.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, but the description goes well beyond them: it defines the exact idempotency key (environment_id + git_sha, in-flight states queued/building/deploying/verifying), the `created: false` sentinel, and the one-active-deployment-per-environment invariant that causes refusal.

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?

Front-loaded with purpose, then idempotency semantics, then next steps — a sensible ordering with no filler. The recap of where `app_id` and `environment_id` come from is mildly redundant with the schema descriptions, costing a little tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, it supplies everything needed: inputs, the concurrency invariant, what the call returns (a deployment, possibly with `created: false`), and which sibling tools to use afterwards. No material gap remains.

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%, so the baseline is 3, but the description adds domain meaning the schema does not: that `environment_id` denotes production or a development/staging environment the app may or may not have, and that `git_ref` is display-only metadata. It does not mention `organization_id`, but the schema documents that fully.

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 a specific verb and outcome ('Triggers a manual deployment of `git_sha` to one of an app's environments') and anchors it to a concrete mental model ('exactly like the Deploy button in the Meridian web app'). An agent can distinguish this from deployment_get, deployments_list, and deployment_rollback without opening any 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?

Explicitly routes the agent after the call: 'Use `deployment_get` to poll the resulting `deployment_id` for status, and `deployments_list`/`logs_tail` for history and live logs.' It also states a when-not condition — a different `git_sha` while a deployment is active is refused.

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

All Meridian toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources