Store a personal access token for HTTP git authentication. Returns confirmation (token value is never echoed).
| Name | Required | Description | Default |
|---|---|---|---|
| token | No | Personal access token to store. | |
| workingDirectory | No | Git repo path. Default current directory. | . |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Only discloses that token value is never echoed. With no annotations, misses critical details: is it idempotent? Does it overwrite? Any prerequisites? Minimal transparency for a security-sensitive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words, front-loaded. Efficient communication.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple store operation, but missing details like return format (confirmation type) and behavior on repeated calls. No output schema to compensate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with descriptions. Description adds no extra meaning beyond schema, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it stores a personal access token for HTTP git authentication. Distinguished from sibling tools like set_ssh which handles SSH keys.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage context (HTTP git auth) but does not explicitly compare with alternatives or state when not to use. Provides clear context but no exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.