Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Get Git Overview

getGitOverview
Read-only

Reads a running app's Git working tree—branch, changes, and recent commits—directly inside its container to verify repository state instead of relying on deploy records.

Instructions

Read the working tree of a development app: branch, changes and recent commits. Reads the repository inside the running container by pod exec, so it is ground truth rather than the deploy record. Returns {ok:false, reason} when the app has no repo, no pod, or no git.

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": "getGitOverview"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
limitNo
regionNo
appSlugYes
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds meaningful behavior beyond that: it reads via pod exec inside the running container, is ground truth rather than deploy metadata, and returns {ok:false, reason} for missing repo, pod, or git. It does not mention latency, auth requirements, or the full success payload.

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 compact sentences that front-load the purpose, then add the important source caveat and error contract. Every sentence contributes useful information with no filler.

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?

There is no output schema, so the description should carry more of the return and parameter contract. It names the main returned areas and one failure shape, but it omits success-field details and all parameter meanings, especially env, limit, and region, despite 0% schema description coverage.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the five parameters, but it never mentions workspaceSlug, appSlug, env, limit, or region. 'Development app' only vaguely gestures at the env parameter and is ambiguous because env also permits production and preview.

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?

States a specific verb and resource: read the working tree of a development app, returning branch, changes, and recent commits. It also distinguishes the data source from the deploy record. It does not explicitly differentiate itself from closely related siblings such as getGitDiff or listBranches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: inspect an app's current in-container git state. However, there is no explicit guidance on when to choose this over getGitDiff, listBranches, or the commit/stage/checkout tools. The phrase 'development app' also is not reconciled with an env parameter that allows production and preview.

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