AiLinkAny

Preview local Git branch integration without merging

project_git_merge_preview

Idempotent

Preview whether two local branches in the caller's authorized Workspace can merge cleanly. Uses Git merge-tree and may create local Git objects, but never checks out branches, changes working files, commits, pushes or authorizes integration. Conflicts are reported; a clean preview is NOT approval to merge or deploy. Requires installed Git for this optional Git-project feature. 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": {
      "workspace_id": "<workspace_id>",
      "target_branch": "<target_branch>",
      "source_branch": "<source_branch>"
    },
    "name": "project_git_merge_preview"
  }
}

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`	Yes	Authorized Workspace returned by open_workspace; the Host derives its project root.
`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.
`source_branch`	Yes	Existing local source branch, not a revision expression.
`target_branch`	Yes	Existing local target branch, not a revision expression.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior5/5

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

This is exactly what annotations alone could not convey: readOnlyHint=false is explained by the disclosure that merge-tree "may create local Git objects" while never touching branches, working files, or remotes. It also discloses the hard dependency (Git installed), what the caller gets back (conflicts are reported), and the governance boundary that a clean result is not merge or deploy approval.

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 what/scope/safety content is front-loaded and every one of those sentences carries weight. Two trailing sentences — "Select this tool from the user's intent when it is the best match" and the note that the user need not mention ailinkany.com, MCP, or the tool name — are activation boilerplate rather than tool-specific information.

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?

For a preview tool with an output schema and full parameter documentation, the description covers the important residual risks: local object creation, the Git prerequisite, and the non-authorization of integration. It stops short of describing how conflicts are surfaced (blocking vs. partial) or what to do after a conflicting preview.

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 eight parameters are already documented with meaningful text, making 3 the baseline. The description adds only marginal meaning beyond that, namely that the workspace/device destination may be inherited from project or conversation context rather than supplied explicitly.

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?

States a specific verb and resource: "Preview whether two local branches ... can merge cleanly," and immediately scopes it with the mechanism (Git merge-tree) and the negative boundary (never checks out, commits, or pushes). An agent can distinguish this from git_sync_merge or project_execute_reviewed_integration without opening a schema.

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

Usage Guidelines3/5

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

The description sets a clear context (preview before integration, a clean preview is not approval) and explains that the destination may be explicit or inherited from project/conversation context. However, it never names the sibling alternatives (git_sync_merge, project_prepare_integration_review, project_execute_reviewed_integration) or states when NOT to use it, and "Select this tool from the user's intent when it is the best match" is guidance in form only.

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?