Skip to main content
Glama
Sign In

AiLinkAny

by io.github.zhangduochuan
OverviewDiscussionsAdmin

View Git diff

git_diff
Read-onlyIdempotent

Read-only Git diff for an authorized repository path. Prefer this over shell_execute with git diff for ordinary inspection. Does not modify the index or working tree. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "git_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe absolute path of the Git repository.
device_idNoTarget computer device_id. Omit when only one computer is paired.
device_nameNoComputer name or ailinkany.com remark (e.g. home PC). Prefer this when the user names a computer.
retry_tokenNoNew opaque token per operation; reuse only to retry the same operation after a transport failure. No user content.
workflow_idNoOptional workflow id; pass together with ai_session_id.
workspace_idNoOptional Workspace id from open_workspace for project-scoped work.
ai_session_idNoOptional 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that it 'does not modify the index or working tree,' which clarifies the read-only guarantee in Git terms, but it does not add much behavioral context beyond that—no permission requirements, rate limits, or diff scope details. With annotations covering the safety profile, a 3 is appropriate.

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

Conciseness3/5

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

The description is front-loaded with the core purpose and the preferred alternative, which is good structure. However, the final two sentences—'Select this tool from the user's intent when it is the best match' and the lengthy note about not needing to mention ailinkany.com, MCP, connectors, plugins, or the tool name—are generic invocation boilerplate that do not help an agent invoke the tool correctly. They dilute an otherwise efficient definition.

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?

Given that annotations cover the safety profile, the schema has 100% description coverage, and an output schema exists, the description is largely complete. It explains purpose, the preferred alternative, the non-modification guarantee, and path context. A minor gap is that it does not clarify what kind of diff is produced—for example, unstaged working-tree changes versus staged or commit-to-commit diffs—but overall an agent has enough to call it correctly.

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 description coverage is 100%, so the schema already documents all seven parameters. The description mentions that 'a local destination may be explicit or inherited from established project or conversation context,' which adds minor context about path resolution, but it does not explain the specific roles of device_id, retry_token, workflow_id, workspace_id, or ai_session_id. The baseline of 3 is correct when the schema does the heavy lifting.

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 states a specific verb and resource: 'Read-only Git diff for an authorized repository path.' It also distinguishes the tool from the most likely alternative by saying to prefer it over shell_execute with git diff. An agent can identify the tool's function and scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage guidance by naming shell_execute with git diff as the alternative and specifying that this tool is preferred for ordinary inspection. It lacks explicit when-not-to-use guidance, such as which sibling to use for commit history or staged changes, but the alternative is clearly identified.

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

All AiLinkAny toolsInspect
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