Skip to main content
Glama
Sunwood-ai-labs

aira-mcp-server

get_status

Retrieve Git repository status information using the specified absolute path to analyze changes and prepare for commit message generation.

Instructions

Gitのステータス情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesGitリポジトリの絶対パス

Implementation Reference

  • Exports createGetStatusHandler function that returns the ToolHandler for 'get_status'. Includes name, description, inputSchema, and the async handler logic: validates 'path' arg, calls gitService.getStatus(path), returns JSON-formatted status as text content.
    export function createGetStatusHandler(gitService: GitService): ToolHandler {
      return {
        name: "get_status",
        description: "Gitのステータス情報を取得します",
        inputSchema: {
          type: "object",
          properties: {
            path: {
              type: "string",
              description: "Gitリポジトリの絶対パス"
            }
          },
          required: ["path"]
        },
        handler: async (args) => {
          try {
            if (!args || typeof args !== 'object' || !('path' in args) || typeof args.path !== 'string') {
              throw new McpError(
                ErrorCode.InvalidParams,
                "path parameter is required and must be a string"
              );
            }
    
            const status = await gitService.getStatus(args.path);
            return {
              content: [{
                type: "text",
                text: JSON.stringify(status, null, 2)
              }]
            };
          } catch (error) {
            throw new McpError(
              ErrorCode.InternalError,
              `Failed to get git status: ${error}`
            );
          }
        }
      };
    }
  • Input schema definition for the get_status tool: object with properties {path: string (required)}.
    inputSchema: {
      type: "object",
      properties: {
        path: {
          type: "string",
          description: "Gitリポジトリの絶対パス"
        }
      },
      required: ["path"]
    },
  • Registers the get_status ToolHandler in the ToolHandlers class's internal Map during constructor initialization.
    this.handlers = new Map([
      ['get_status', createGetStatusHandler(gitService)],
      ['create_commit', createCreateCommitHandler(gitService)]
    ]);
  • GitService.getStatus(path) method, which delegates to statusManager.getStatus(path). Called by the tool handler.
    async getStatus(path?: string) {
      return this.statusManager.getStatus(path);
    }
  • src/index.ts:46-47 (registration)
    Dispatches 'get_status' tool calls to toolHandlers.handleGetStatus in the main server request handler.
    case "get_status":
      response = await toolHandlers.handleGetStatus(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While '取得します' (get/retrieve) implies a read operation, the description doesn't specify what 'Git status information' includes, whether authentication is required, potential rate limits, or what format the information returns. This leaves significant behavioral gaps.

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 a single, efficient Japanese sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool with one parameter and gets straight to the point.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'Git status information' includes, what format it returns, or any behavioral constraints. Given the complexity of Git operations and lack of structured documentation, more context is needed for the agent to use this tool effectively.

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?

The input schema has 100% description coverage, with the single parameter 'path' clearly documented as 'Gitリポジトリの絶対パス' (absolute path to Git repository). The tool description doesn't add any parameter information beyond what's already in the schema, so the baseline score of 3 is appropriate.

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 clearly states the action ('取得します' - get/retrieve) and resource ('Gitのステータス情報' - Git status information), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'create_commit', which is a different operation but related to Git repository management.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or relationship to the sibling 'create_commit' tool, leaving the agent without usage direction.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sunwood-ai-labs/aira-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server