Skip to main content
Glama
Sign In
omni-mcp-server

omni-mcp-server

by bitofacoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

git_diff

View line-by-line code changes in your Git repository, showing unstaged differences by default. Optionally inspect staged changes.

Instructions

Run git diff to see exact line-by-line code changes. Shows unstaged changes by default.

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_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
stagedNoIf true, runs git diff --staged to see staged changes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It states the default mode but fails to disclose that it is a read-only operation, what the output format is, or any potential side effects (e.g., large diffs).

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 sentences, no wasted words. The first sentence defines the core purpose, and the second clarifies the default behavior. Ideal for a simple tool.

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 tool with one boolean parameter and no output schema, the description adequately covers what the tool does and its default behavior. It lacks details about output format but this is standard git knowledge. Overall sufficient.

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 schema covers the single parameter (staged) with a description. The tool's description reiterates the default (unstaged) and implies the parameter's effect, but adds no additional meaning beyond the schema. Baseline 3 is appropriate given 100% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool runs 'git diff' to show 'exact line-by-line code changes', which is specific and distinguishes it from sibling tools like git_status (summary) and git_log (history).

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?

The description notes the default behavior (unstaged changes) and the staged parameter, but provides no guidance on when to use this tool versus alternatives like git_status or git_log, nor mentions any prerequisites or conditions.

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