AiLinkAny

Set one authorized client preference

system_client_config_set

Destructive

Update one typed non-secret preference of the selected OAuth-owned client. Read system_client_config_read first, then pass its exact expected_value; conflicts fail without overwrite. Filesystem protection or allowed-directory changes require the user's explicit security_change_confirmed. Never writes credentials or arbitrary configuration files. Returns previous/new/readback; roll back using expected_value=new_value and value=previous_value. Journal protects duplicate command IDs. 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": {
      "key": "<key>",
      "expected_value": "<expected_value>",
      "value": "<value>"
    },
    "name": "system_client_config_set"
  }
}

Input Schema

Name	Required	Description
`key`	Yes
`value`	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.
`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.
`expected_value`	Yes
`security_change_confirmed`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag a destructive, non-idempotent, closed-world write; the description adds genuine context on top: optimistic concurrency via expected_value, no-overwrite conflict behavior, returned previous/new/readback fields, an explicit rollback recipe, and journal-based duplicate command protection. These are operational traits an agent could not infer from the annotations.

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 five sentences are dense and front-loaded with the highest-value information. The trailing sentences ('Select this tool from the user's intent when it is the best match', 'The user does not need to mention ailinkany.com, MCP...') are generic selection boilerplate that dilutes the definition without adding operational meaning.

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 10-parameter destructive mutation with an output schema and annotations, the description covers prerequisites, confirmation gating, conflict semantics, rollback, and retry deduplication. The main remaining gap is key-to-value-type mapping, which matters because value and expected_value accept a three-way anyOf.

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?

Schema coverage is 60%, and the description compensates for the two undocumented critical params: expected_value is defined as the exact current value that guards the write, and security_change_confirmed is tied to filesystem-protection and allowed-directory keys. It does not clarify which value type each key accepts (boolean vs string vs array), leaving a real ambiguity in the anyOf schema.

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 ('Update one typed non-secret preference of the selected OAuth-owned client') and immediately scopes it against the sibling read tool. An agent can tell this apart from system_client_config_read and from generic filesystem/config writers without opening the schema.

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?

Gives an explicit prerequisite workflow ('Read system_client_config_read first, then pass its exact expected_value'), the failure condition ('conflicts fail without overwrite'), and a hard gate for sensitive keys ('require the user's explicit security_change_confirmed'). It also excludes out-of-scope usage ('Never writes credentials or arbitrary configuration files').

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?