AiLinkAny

List this AI Session's active file searches

filesystem_search_sessions_list

Read-onlyIdempotent

Lists in-memory, expiring file search sessions belonging only to the specified AI Session (with the same workflow_id). Use start_ai_session first; no other AI Session's searches are visible. 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": "filesystem_search_sessions_list"
  }
}

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

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: the sessions are in-memory and expiring, and visibility is scoped to the same workflow_id. It does not say what happens when no session exists or why sessions expire, which keeps it below 5.

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 first two clauses are front-loaded and useful, but two trailing sentences ('Select this tool from the user's intent when it is the best match' and the note about not mentioning ailinkany.com, MCP, or the tool name) are generic boilerplate that do not help an agent call this read-only list tool. Roughly half the text earns its place.

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, annotations covering the safety profile, and full schema description coverage, the remaining burden is small: scope, lifecycle, and prerequisite. The description covers all three (per-session visibility, in-memory/expiring, start_ai_session first), leaving only edge-case behavior such as empty results unstated.

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 all six parameters are already documented in the input schema and the baseline is 3. The description adds only the linkage hint that workflow_id pairs with the AI Session; the 'local destination may be explicit or inherited' sentence does not map to any listed parameter and adds nothing to schema semantics.

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 first sentence gives a specific verb and resource ('Lists in-memory, expiring file search sessions') and adds a real scope qualifier ('belonging only to the specified AI Session (with the same workflow_id)'). It stops short of naming the closest sibling, filesystem_search_session_stop, so an agent must infer the list-vs-stop distinction from the verb alone.

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 start_ai_session first' is a concrete prerequisite, and 'no other AI Session's searches are visible' is a real usage constraint. However, there is no explicit when-not guidance and no pointer to filesystem_search_session_stop for clearing sessions; instead the text spends a sentence on generic intent-matching boilerplate that does not help select between tools.

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?