Skip to main content
Glama

capture_git_evidence

Safely inspects and captures Git state—status, branch, HEAD commit, and diff checks—into an evidence bundle without mutating the repository.

Instructions

Safely inspects and captures Git state (status, branch, HEAD commit, diff check) without mutating the repo.

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": {
      "bundleId": "<bundleId>"
    },
    "name": "capture_git_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleIdYesThe unique identifier of the evidence bundle.
workspaceNameNoOptional registered workspace/package name (defaults to primary root).
workspacePathNoOptional workspace path hint if running outside default cwd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / workspaceName
      Added value: +{
      +  "description": "Optional registered workspace/package name (defaults to primary root).",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the most important trait, that it never mutates the repo, which is genuinely useful. It stops short of stating where the captured state goes (appended into the given bundleId? failing if absent?), permission requirements, or error behavior, leaving real gaps for a stateful evidence tool.

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?

A single front-loaded sentence that names the action, the data captured, and the safety guarantee with zero wasted wording.

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?

Three parameters with full schema coverage and no output schema keep the bar modest, but the description omits what the capture actually produces or how it interacts with an existing evidence bundle, which matters for a tool named around evidence capture.

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 description coverage is 100%, so bundleId, workspaceName, and workspacePath are already documented in the schema. The description adds no extra meaning about how the bundle target or workspace hint affect capture behavior, so baseline 3 applies.

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?

Specific verb+resource: 'inspects and captures Git state' with enumerated fields (status, branch, HEAD commit, diff check). This clearly separates it from sibling evidence captures like capture_ast_evidence and capture_sbom_evidence by naming the resource (Git) and the exact data captured.

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?

Implied usage only — an agent can infer it is the tool for Git-derived evidence, but there is no explicit when-to-use, no prerequisites (e.g., must a bundle exist first via create_evidence_bundle?), and no stated alternatives or exclusions.

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