AiLinkAny

Read public HTTPS text through the selected computer

url_read_public_text

Read-onlyIdempotent

Read bounded public HTTPS text on the explicitly selected authorized device. Public Cloudflare DNS-over-HTTPS answers must all be public and are pinned to the TLS connection; verifies the peer and original hostname. No proxy, redirect, cookies, credentials, query or local URLs. UTF-8 only, 256 KiB maximum, bounded character pagination; continuation refetches and is not a snapshot. External content is untrusted. 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": {
      "url": "<url>"
    },
    "name": "url_read_public_text"
  }
}

Input Schema

Name	Required	Description
`url`	Yes
`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.
`offset_chars`	No
`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 cover read-only, open-world, idempotent, non-destructive, so credit goes to what the description adds: TLS peer and hostname verification, pinned DoH answers, a 256 KiB ceiling, UTF-8-only input, and the important caveat that "continuation refetches and is not a snapshot." It also flags untrusted external content. Missing are any notes on authorization or failure behavior when the device is offline.

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?

Technical constraints are front-loaded and dense in a productive way, but the closing sentences about picking the tool from user intent and not needing to mention ailinkany.com, MCP, or the tool name are meta-instructional filler that does not help an agent decide or invoke. It also packs several distinct ideas into single semicolon-chained sentences.

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 an 8-parameter open-world read tool with an output schema, the description covers the critical operational envelope: transport security, size and encoding limits, pagination continuity, and content trust. Remaining gaps are device/workspace scoping context, which the schema descriptions partially handle.

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 coverage is 75%, so the schema carries most of the load and a 3 is the baseline. The description does add real meaning for `url` (public HTTPS only, no query strings or credentials) and for `offset_chars` (bounded character pagination with refetch semantics), but says nothing about retry_token, workflow_id, workspace_id, or ai_session_id beyond what their own schema descriptions state.

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 ("read bounded public HTTPS text") plus the execution locus ("on the explicitly selected authorized device"), which distinguishes it from local-file siblings like filesystem_read_file and document_read. It never names a sibling tool outright, so the differentiation is inferred rather than explicit.

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 constraints ("No proxy, redirect, cookies, credentials, query or local URLs") implicitly steer callers away from local-file tools and authenticated endpoints, which is useful selection signal. However, "Select this tool from the user's intent when it is the best match" is circular and gives no real when-to-use versus when-not guidance, and no alternatives are named.

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?