AiLinkAny

Read safe local client configuration

system_client_config_read

Read-onlyIdempotent

Read all non-secret local preferences of the selected authorized Windows client: autostart and initialization, filesystem protection and authorized directory paths, endpoint mode, locale, activity times, version and timestamp. OAuth-owned device selection is required. Credentials, endpoint secrets and registry data are excluded; this tool only reads. 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": "system_client_config_read"
  }
}

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

B3.2/5.0

Behavior3/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 covered. The description does add useful scope boundaries — credentials, endpoint secrets, and registry data are excluded — plus the OAuth device-selection requirement. It stops short of describing failure modes or what happens when no device 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.

Conciseness3/5

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

The field enumeration is front-loaded and earns its place, but the trailing sentences ('Select this tool from the user's intent when it is the best match' and the note about not needing to mention ailinkany.com, MCP, a connector, or a plugin) are generic boilerplate that dilutes the signal.

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 an output schema present, the description need not explain return values, and it correctly focuses on scope and exclusions. For a read-only, zero-required-parameter tool with full schema coverage, the definition is nearly complete; only explicit sibling routing guidance is missing.

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 all six parameters are already documented in the schema, making 3 the baseline. The description adds only marginal meaning, noting that the destination may be explicit or inherited from project/conversation context, which loosely supports the optional device_id/device_name/workspace_id parameters.

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 opens with a specific verb and resource ('Read all non-secret local preferences of the selected authorized Windows client') and enumerates the concrete fields returned (autostart, filesystem protection, endpoint mode, locale, activity times, version). The phrase 'this tool only reads' implicitly separates it from the system_client_config_set sibling, though it never names that sibling explicitly.

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

Usage Guidelines2/5

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

'Select this tool from the user's intent when it is the best match' is vacuous and gives no real when-to-use criteria. There is no statement of when NOT to use it versus system_client_config_set, system_info, or get_configuration, and no prerequisites beyond the passing note that OAuth-owned device selection is required.

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?