Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Stage Git Files

stageGitFiles
Destructive

Stages specified repository paths inside a development app's running container, adding their current contents to the Git index for the next commit and returning Git output.

Instructions

Add the current contents of the given paths to the index, ready for the next commit. Works only on a development app: any other app answers 403 read_only. Runs git in the app's running container and returns its output.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>"
    },
    "name": "stageGitFiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the description's job is to add context, and it does: the dev-only 403 restriction and the fact that git runs inside the app's running container. It does not note that staging replaces any previously staged content for those paths, which is relevant given the destructive hint.

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?

Three short sentences, front-loaded with the action, then the constraint, then the execution/return note. No filler or redundancy.

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

Completeness3/5

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

With five parameters, a nested request body and no output schema, the definition covers the action and the key constraint but leaves the return value as a vague "returns its output" and never explains the required workspaceSlug/appSlug identifiers. Adequate to call correctly in the common case, but with visible gaps.

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 coverage is only 20%, so the description needs to carry parameter meaning. It clarifies the intent of requestBody.paths ("current contents of the given paths to the index") and effectively explains env via the development-only rule, but workspaceSlug, appSlug and region receive no explanation anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Add the current contents of the given paths to the index, ready for the next commit" gives a precise verb-plus-resource and disambiguates the git-staging operation from commit/unstage siblings through the phrase "ready for the next commit." It stops short of naming those siblings, so it is clear but not explicitly differentiated.

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 gives a hard usage boundary: "Works only on a development app: any other app answers 403 read_only," which tells the agent when not to call it and why the env parameter matters. It offers no direct alternative pointer (e.g., unstageGitFiles for reversal), which keeps it below a 5.

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