Skip to main content
Glama
Sign In
CodeForgeX

CodeForgeX

by kirubeshvarman28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_repository_status

Inspect current Git status to show branch, clean flag, and lists of modified, staged, or untracked files.

Instructions

Inspect the current Git repository status (modified, staged, untracked files).

Returns: JSON string with branch, clean flag, and lists of modified/staged/untracked files.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_repository_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral transparency burden. It communicates a read-only intent through 'Inspect' and explicitly describes the returned JSON structure (branch, clean flag, file lists). It does not mention error behavior or explicitly state 'does not modify files,' but for a simple status-inspection tool this is adequate.

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?

The description is only two sentences, with the primary purpose front-loaded and the return format in a compact second sentence. There is no filler, repetition, or unnecessary detail.

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

Completeness4/5

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

For a parameterless, read-only status tool, the description covers what it does and what it returns, and an output schema is present to formalize the response. Missing error-condition details are a minor gap given the tool's simplicity.

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?

The tool has zero parameters, so there is no parameter schema ambiguity to resolve; the baseline 4 applies. The description appropriately omits parameter details because none exist.

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?

The description uses a specific verb ('Inspect') and resource ('current Git repository status'), with a parenthetical listing modified/staged/untracked files. It clearly states what the tool does and the status focus implicitly distinguishes it from get_git_diff, though it does not explicitly name or contrast that sibling.

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?

The usage context is implied: use this when you need the current repository status such as modified, staged, or untracked files. However, there is no explicit guidance on when to choose this over get_git_diff or other siblings, so the agent must infer the appropriate selection.

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