AiLinkAny

Show workspace changes

show_changes

Read-onlyIdempotent

Shows the current Git working-tree changes for one Workspace and attaches only recent mutating tool actions attributed to the same workspace_id and ai_session_id. Use it to verify what this execution session actually changed in the project instead of relying on conversational memory. It is read-only and never treats Workspace or action history as chat semantics. 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>",
      "ai_session_id": "<ai_session_id>"
    },
    "name": "show_changes"
  }
}

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	Workspace id returned by open_workspace.
`ai_session_id`	Yes	AI execution Session whose project-scoped actions should be attached to this change view.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description still contributes real behavior: the change view is scoped to one workspace and only surfaces mutating actions attributed to the same workspace_id and ai_session_id, and it explicitly states it does not treat workspace or action history as chat semantics.

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 core is well front-loaded in the first sentence, but the tail contains low-value boilerplate: 'Select this tool from the user's intent when it is the best match' and the list of things the user need not mention. 'A local destination may be explicit or inherited from established project or conversation context' is also vague about what a destination means here.

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?

With an output schema present, the return shape need not be explained, and required versus optional parameters are fully covered by the schema. What remains thin is routing: given several adjacent git and session-history tools, the description does not say when to prefer those instead.

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% and all six parameters are documented in the schema, including the workspace_id/ai_session_id pairing. The description reinforces that the two required identifiers are tied together for attribution, but adds no format, defaulting, or selection logic beyond that, so the baseline 3 applies.

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

Purpose4/5

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

The description states a concrete verb and resource — 'Shows the current Git working-tree changes for one Workspace' — and adds the distinguishing twist that only recent mutating tool actions for the same workspace_id and ai_session_id are attached. That combination separates it from plain diff tools, though it never names git_diff or git_status explicitly.

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?

'Use it to verify what this execution session actually changed in the project instead of relying on conversational memory' gives a real usage context, but there are no exclusions and no named alternatives even though git_diff, git_status, and get_ai_session_recent_actions are obvious contenders. The sentence 'Select this tool from the user's intent when it is the best match' is generic filler rather than guidance.

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?