Skip to main content
Glama
Example MCP Server

Example MCP Server

by Ranjith63812

git_status

Check a Git repository's status, current branch, changed files, and commit history to understand its state before making changes.

Instructions

Check the status of a git repository, including current branch, changed files, and commit history

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

Input Schema

NameRequiredDescriptionDefault
pathNoOptional path to the git repository (defaults to current directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read but never states the operation is read-only and non-destructive, does not describe failure behavior (not a repo, detached HEAD, no commits), and says nothing about output volume or formatting despite listing three distinct data categories.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted wording. Slightly loose enumeration ('commit history') but nothing that could be cut without losing meaning.

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 low-complexity single-parameter read tool with no output schema, the description is mostly sufficient because it names the returned fields. The remaining gap is failure-mode and read-only disclosure, which is modest given the tool's simplicity.

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?

One optional parameter with 100% schema description coverage, so the schema already explains the path and its default. The description adds no syntax, path resolution, or behavior details beyond what the schema documents, 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?

States a specific verb (check) and resource (git repository status) and enumerates the concrete outputs: current branch, changed files, commit history. An agent can immediately tell this is the git working-tree inspector from the sibling set (file_reader, ping, system_info), though the description never explicitly contrasts against them.

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?

There is no when-to-use guidance, no preconditions, and no named alternative. It does not say whether the path must already be a git repo, what happens when it isn't, or when an agent should prefer reading files directly over inspecting status.

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