AiLinkAny

Read computer image

filesystem_read_image

Read-onlyIdempotent

Reads a PNG, JPEG, GIF, or WebP image from the target computer and returns it as a native MCP image content block. Use this for local image inspection or analysis instead of reading the file as text or switching to another computer-control connector. Images are limited to 4 MiB and remain subject to the configured filesystem allowlist. 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_image"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	The absolute PNG, JPEG, GIF, or WebP image path to read.
`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

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is set. The description adds genuinely new behavioral facts: a 4 MiB image size cap and that reads remain subject to the configured filesystem allowlist, both of which affect whether a call will succeed.

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 well-formed and front-loaded with purpose, limits, and the alternative. The trailing selection boilerplate ('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 routing chrome that does not help an agent invoke this tool and dilutes the useful content.

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?

For a 7-parameter read tool with full schema coverage, rich annotations, and an output schema, the description covers the essentials: format support, return shape, size limit, and allowlist constraint. Only device-targeting nuance is left implicit, and the schema carries that.

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% across all 7 parameters, so path, device_id, device_name, retry_token, and session/workspace ids are already fully documented. The description only hints that the 'local destination may be explicit or inherited from established project or conversation context,' which adds marginal meaning over the schema's own 'Omit when only one computer is paired.'

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

Purpose5/5

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

States a specific verb and resource ('Reads a PNG, JPEG, GIF, or WebP image'), names supported formats, and describes the return type ('native MCP image content block'). This clearly separates it from the sibling filesystem_read_file, which would return text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use this 'for local image inspection or analysis instead of reading the file as text or switching to another computer-control connector' — a direct when-to-use plus named alternatives. The only addition an agent might want (how to pick device_id vs device_name) is covered in the schema.

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?