Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

git_stage

Destructive

Stages selected workspace file paths for commit, requiring GUI approval before changes are applied.

Instructions

Stage selected workspace file paths. Requires GUI approval.

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": {
      "files": "<files>"
    },
    "name": "git_stage"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesRelative files to stage

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write nature is known. The description adds a genuinely useful behavioral fact beyond that — "Requires GUI approval" — meaning a call may block or fail pending human confirmation. It does not say what gets modified (the index), what happens on rejection, or whether existing staged changes are affected, so the disclosure is partial.

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?

Two short sentences, front-loaded with the action and followed by the approval prerequisite. 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?

For a one-parameter tool with full schema coverage and annotations, this is close to adequate, and the approval note covers the biggest surprise. However, ambiguity remains about whether whole files or individual hunks are staged, and what happens when the GUI approval is denied.

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%, with the single "files" parameter documented as relative files to stage and bounded by minItems/maxItems. The description's "selected workspace file paths" adds only the workspace-relative framing, so it neither needs to nor does add much beyond the schema.

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?

"Stage selected workspace file paths" gives a specific verb (stage) and resource (workspace file paths), which an agent can distinguish from git_commit or git_diff. It stops short of explicitly naming the sibling it precedes, so it is clear but not fully differentiated.

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 by "stage" and by "selected", which signals the agent must pick specific paths rather than stage everything. There is no explicit when-to-use/when-not guidance and no mention that staging precedes git_commit, so an agent must infer the workflow.

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