Skip to main content
Glama
Sign In
daimonos

daimonos

by beardfaceguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

git

Execute version control operations including status, log, diff, branch, add, commit, push, pull, and checkout, passing all arguments directly through to the underlying command.

Instructions

Git operations. Commands: status, log, diff, branch, add, commit, push, pull, checkout. All args besides 'command' are passed through.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/5

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

The description claims 'All args besides 'command' are passed through,' but the input schema has no parameters, creating a contradiction. No behavioral traits (e.g., destructive actions, authentication needs, rate limits) are disclosed, leaving the agent without critical safety information.

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?

The description is concise with two sentences that quickly convey the purpose. It front-loads the main idea ('Git operations') and lists commands efficiently, though the pass-through statement could be clearer.

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 that wraps Git commands, the description should explain how to invoke specific commands and handle arguments. The missing 'command' parameter in the schema and lack of output format details leave the tool incomplete. Without annotations, the description fails to provide a complete behavioral picture.

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?

With schema coverage at 100% (no parameters), the baseline is 3. The description adds information about pass-through arguments, but the mismatch between the implied 'command' parameter and the empty schema reduces clarity. It hints at semantics but fails to define how to pass parameters correctly.

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 'Git operations' and lists common Git commands, making it clear that this tool executes Git subcommands. It distinguishes from sibling tools like cargo or gh by specifying Git. However, it lacks specificity about the exact scope beyond listing commands.

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 on when to use this tool versus alternatives like exec or execute_script. The description does not mention prerequisites, typical use cases, or scenarios where this tool is preferred.

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