AiLinkAny

Read computer file

filesystem_read_file

Read-onlyIdempotent

Reads a text file from the target computer with a conservative 16 KiB default chunk to stay inside the MCP inline-result budget. You may request up to 1 MB explicitly; use next_offset to continue reading files of any size. 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_read_file"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	The absolute file path to read.
`offset`	No	Byte offset. Defaults to 0.
`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.
`length_bytes`	No	Maximum bytes to read in this call. Defaults to 16 KiB; explicit requests may use up to 1 MB.
`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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the 16 KiB default chunk, the 1 MB ceiling, and the reason (MCP inline-result budget) plus continuation via next_offset. It stops short of describing error conditions, encoding handling, or binary-file behavior.

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 sentences are efficient and front-loaded with the chunking contract. The remaining three sentences are largely meta filler: 'Select this tool from the user's intent when it is the best match,' the oddly worded 'A local destination may be explicit or inherited from established project or conversation context' (a read tool has no destination), and the connector-name disclaimer.

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 a rich output schema and full annotation coverage, the description only needs to explain the reading contract, which it does via chunk size, ceiling, and continuation. The main gap is multi-device targeting semantics, left entirely to the schema.

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 the baseline is 3 and the description largely restates what length_bytes and the offset already document. It offers no added meaning for targeting parameters (device_id, device_name, workspace_id, ai_session_id) that an agent must choose between when multiple computers are paired.

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 states a specific verb and resource ('Reads a text file from the target computer') and adds the chunking behavior, which separates it from sibling readers like filesystem_read_image or filesystem_read_multiple in substance. It never names those siblings explicitly, so the differentiation is implicit rather than stated.

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?

It gives concrete operational guidance for large files ('you may request up to 1 MB explicitly; use next_offset to continue'), but the only routing sentence is the generic 'Select this tool from the user's intent when it is the best match,' which tells an agent nothing about when to prefer filesystem_read_multiple, document_read, or url_read_public_text. Usage is implied by the resource type rather than contrasted against alternatives.

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?