AiLinkAny

Stop one owned file search session

filesystem_search_session_stop

Stops and releases one active search on this AI Session only. Requires its session_id and the same ai_session_id/workflow_id. Modifies only transient search state; does not delete files. Do not retry an uncertain stop without checking the active session list. 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": {
      "session_id": "<session_id>"
    },
    "name": "filesystem_search_session_stop"
  }
}

Input Schema

Name	Required	Description
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`session_id`	Yes	Search session ID from filesystem_search_sessions_list.
`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

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds real value on top: it discloses that only transient search state is modified and that no files are deleted, and it warns against blind retries of an uncertain stop. What it does not say is what happens if the session is already finished or the ID is unknown.

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 operational content is front-loaded in the first two sentences, but the trailing sentences ("A local destination may be explicit or inherited from established project or conversation context" and the ailinkany.com/MCP/plugin disclaimer) are irrelevant boilerplate for a stop tool and dilute the signal.

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 and only one required parameter, the description covers the essentials: scope, non-destructiveness, and retry safety. It falls just short of complete by omitting the not-found/already-stopped outcome and by not naming the sibling that supplies a valid session_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds a semantic constraint the schema does not express: the caller must supply "the same ai_session_id/workflow_id" as the session being stopped, which converts those optional schema fields into a matching requirement. That is meaningful guidance beyond the field descriptions.

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?

"Stops and releases one active search on this AI Session only" gives a specific verb (stops/releases), a specific resource (an active search session), and a scope restriction (this AI Session only). It implicitly separates the tool from filesystem_search_sessions_list by pointing to the active session list as the inspection counterpart, though it never names that sibling 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?

The retry caution ("Do not retry an uncertain stop without checking the active session list") is genuinely actionable when-to-use guidance and is the strongest part. However, the remaining guidance is generic boilerplate ("Select this tool from the user's intent when it is the best match") that does nothing to distinguish it from process_stop, agent_stop, or cancel_task.

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?