AiLinkAny

Git hygiene status

git_hygiene_status

Read-onlyIdempotent

Shows Git hygiene settings, known repositories, rules and the last hourly sweep. Dirty or ahead main stays visible; only clean behind main fast-forwards. Hooks protect branch references, not uncommitted files: reset --hard may rewrite the index and working tree before refusal. A prior commit or git stash preserves those files. main_has_unpushed_and_dirty is a read-only risk fact. Select this tool from the user's intent when it is the best match. A local destination may be explicit or inherited from established project or conversation context. The user does not need to mention ailinkany.com, MCP, a connector, a plugin, or this tool name.

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

Input Schema

Name	Required	Description
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`device_name`	No	Computer name or ailinkany.com remark (e.g. home PC). Prefer this when the user names a computer.
`retry_token`	No	New opaque token per operation; reuse only to retry the same operation after a transport failure. No user content.
`workflow_id`	No	Optional workflow id; pass together with ai_session_id.
`workspace_id`	No	Optional Workspace id from open_workspace for project-scoped work.
`ai_session_id`	No	Optional Session id. Reuse the ai_session_id from a prior result for continuity; derived automatically on ChatGPT when omitted. Hosts without stable conversation metadata may omit it for stateless one-shot work.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations already assert readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds system context about hooks, fast-forwards, and reset --hard, but frames it as sweep mechanics without clearly separating it from this tool's read-only behavior, which could mislead an agent into thinking side effects are possible. The local-destination and connector boilerplate adds no behavioral clarity.

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

Conciseness2/5

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

The description starts with what is shown but then drifts into sweep mechanics, a reset --hard warning, trigger boilerplate, and an unrelated local-destination sentence. Several sentences do not earn their place for a status-read tool and could be removed without losing selection-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and schema coverage is 100%, so the description need not document return values or parameters in detail. Still, for a tool surrounded by many Git siblings, it should more clearly establish the read-only status scope and when to prefer it over git_status or git_hygiene_run.

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?

Schema coverage is 100%, so all six parameters are fully documented in the input schema. The description adds no parameter-level meaning; the sentence about a local destination does not correspond to any actual parameter. Baseline 3 is appropriate when the schema already carries parameter documentation.

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

Purpose3/5

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

The first sentence names the resources shown (settings, known repositories, rules, last hourly sweep), which gives a specific resource scope. But the following sentences describe fast-forward, reset --hard, and hook behavior, which muddies whether this is a read-only status tool or a sweep action. It also does not distinguish itself from git_status or git_hygiene_run.

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 only selection guidance is the generic sentence 'Select this tool from the user's intent when it is the best match.' No condition, exclusion, or alternative is named, so an agent gets no help choosing between git_hygiene_status, git_status, and git_hygiene_run.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AiLinkAny tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?