AiLinkAny

List paired computers

list_devices

Read-onlyIdempotent

Use this when the user asks which computers are paired, whether they are online, or when the target is unclear among multiple computers. Returns every computer paired with the current account and its connection state. The user does not need to mention ailinkany.com, MCP, a connector, or a plugin. When the user already named a computer, call the requested device tool directly with device_name instead.

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": "list_devices"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ok`	Yes
`devices`	Yes
`default_device_id`	Yes
`selection_required`	Yes
`public_ip_visible_to_ai`	Yes
`location_metadata_visible_to_ai`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by saying it returns every paired computer and its connection state, and that the user does not need to mention ailinkany.com, MCP, a connector, or a plugin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary use case and return behavior, then adds the important alternative-tool routing rule. It is appropriately sized, though the sentence about not needing to mention ailinkany.com, MCP, a connector, or a plugin is slightly meta and could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters, rich annotations, and an output schema, the description covers the key decision points: when to use this tool, what it returns, and when to use a device-specific tool instead. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is no parameter semantics burden. The description correctly does not invent parameter details, and the empty schema is consistent with a no-argument discovery call.

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?

The description states a specific verb and resource: it lists every computer paired with the current account and reports connection state. It also distinguishes this discovery tool from device-specific tools by saying to call the requested device tool directly when the user has already named a computer.

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?

It gives explicit triggers: when the user asks which computers are paired, whether they are online, or when the target is unclear among multiple computers. It also gives an explicit exclusion: when the user already named a computer, use the requested device tool directly with device_name instead.

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?