AiLinkAny

List local connection profiles

connection_profile_list

Read-onlyIdempotent

Lists SSH, Telnet, and serial-console connection profiles configured locally in the ailinkany.com Windows client. Returns only non-secret metadata and whether local credentials are available. It never returns passwords, private-key contents, key passphrases, or local private-key paths. 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

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

Input Schema

Name	Required	Description
`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.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the bar is lower; the description goes beyond them by declaring what is returned (non-secret metadata plus a credential-availability flag) and enumerating what is never returned (passwords, private-key contents, passphrases, private-key paths). That security boundary is genuinely useful context an agent cannot derive from the annotations. It stops short of describing ordering, failure modes, or behavior when no client is paired.

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 core capability and its data-exposure boundary are front-loaded in the first two sentences with no wasted wording. The trailing intent-routing sentences are shorter but partly boilerplate, which keeps it just below fully economical.

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?

This is a simple, all-optional-parameter list tool with full annotation coverage and an output schema, and the description covers purpose, scope, exposure limits, and context-based invocation. An agent has everything needed to decide whether to call it and what it will and will not receive back.

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% and all six parameters are individually documented, so the schema carries the semantic load. The description only adds the general framing that a destination may be inherited from context (relevant to the optional device_id/device_name/workspace_id fields) and says nothing about retry_token or session identifiers beyond what the schema states.

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 description gives a specific verb and resource ('Lists SSH, Telnet, and serial-console connection profiles configured locally in the ailinkany.com Windows client') and bounds the scope to locally configured profiles. It does not explicitly name the sibling that handles a single profile lookup (connection_profile_read), so routing among the profile family is left partly to inference.

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 supplies invocation context — the local destination may be explicit or inherited from project/conversation context, and the user need not name the vendor or tool — which helps an agent recognize the right trigger. However, 'Select this tool from the user's intent when it is the best match' is boilerplate, and there is no explicit when-not condition or named alternative such as connection_profile_read for a single profile.

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?