AiLinkAny

Inspect file metadata and UTF-8 line count

filesystem_stat_extended

Read-onlyIdempotent

Read-only extended metadata, returning size, modified_at, type, file readonly attribute and optional UTF-8 line count for up to 8 MiB. The writable_attribute is based on filesystem attributes, NOT an effective ACL access test. Does not inspect Office/PDF document contents. 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": "filesystem_stat_extended"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Absolute file or directory path.
`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 readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real value on top with the 8 MiB line-count ceiling and the important caveat that the writable attribute reflects filesystem attributes rather than an effective ACL test, which prevents a wrong permission inference. It stops short of describing error behavior (missing path, unreadable file) or encoding nuances for the line count.

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 sentence is front-loaded and dense with useful facts, and the ACL caveat is well-placed. The middle block ('Select this tool from the user's intent when it is the best match... The user does not need to mention ailinkany.com, MCP, a connector, a plugin, or this tool name') is generic invocation boilerplate that adds no decision-relevant information and dilutes the description.

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?

An output schema exists, so return values needn't be spelled out, and with 100% schema coverage the parameters are self-documenting; the description correctly spends its budget on behavioral caveats instead. The remaining gap is disambiguation from filesystem_stat_file, which for a near-duplicate sibling is the one thing an agent most needs.

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 seven parameters are already documented in the schema and the baseline of 3 applies. The description adds only a weak contextual hint that a destination 'may be explicit or inherited from established project or conversation context,' which mildly informs workspace_id/ai_session_id usage but is not tied to any parameter by name.

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 opening sentence names a specific verb and resource and enumerates the returned fields (size, modified_at, type, readonly attribute, optional line count) plus a size bound, so the agent knows exactly what it gets. However, the sibling set contains filesystem_stat_file, an almost identical tool, and the description never names or distinguishes it, leaving the closest ambiguity unresolved.

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?

'Does not inspect Office/PDF document contents' is a genuine when-not signal that implicitly routes binary/document extraction elsewhere. But 'Select this tool from the user's intent when it is the best match' is tautological filler, no alternative tool is named, and nothing says when to prefer filesystem_list_directory or filesystem_read_file over a stat call.

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?