reset_login
Clear stored git credentials by unsetting the credential helper in local git config. Returns confirmation.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workingDirectory | No | Git repo path. Default current directory. | . |
giteasy
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description mentions clearing credentials and returning confirmation but lacks detail on side effects (e.g., re-entry needed) or scope (local vs global).
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?
Extremely concise: one sentence with clear action and outcome; no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description sufficiently covers purpose, input, and return behavior.
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?
Single parameter fully described in schema; description adds no additional meaning beyond the schema's documentation.
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?
Clearly states it clears stored git credentials by unsetting the credential helper, distinguishing it from sibling tools like set_ssh or set_token.
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?
Does not provide guidance on when to use this tool versus alternatives; no context for prerequisites or when clearing is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose. Even similar tools like 'undo_changes' and 'restore_file' differ in scope (all vs single file), and 'find_changes' vs 'show_change' list files vs show diffs. No two tools overlap ambiguously.
Naming Consistency4/5
All tool names follow a verb_noun snake_case pattern. While verbs are not perfectly uniform (e.g., 'get_vault_status' vs 'show_history'), the naming is consistent and predictable, with no mixed camelCase or confusing conventions.
Tool Count4/5
22 tools is on the higher side but appropriate for a comprehensive Git server covering branch management, commits, pushes, credentials, diagnostics, and more. The number is manageable and each tool serves a distinct function.
Completeness3/5
The tool set covers essential operations but has notable gaps: there's no branch listing, pull/merge, or stash functionality. Agents may encounter dead ends when needing these operations, though core workflows like commit and push are well supported.