Well

List paired devices

well_list_paired_devices

Read-only

Use this when the person asks to list paired devices. List the user's own paired devices: the computers whose browser, with the Well extension, the user paired to their Well account with a code sent on WhatsApp. Well fills the user's saved logins only in a paired browser. Call it when the user asks which computers or browsers are paired or connected to Well ("quels appareils sont appairés ?", "show my paired devices", "sur quels ordinateurs Well peut se connecter ?"), and always before well_revoke_device, to find the id of the device to unpair.

Each device carries device_id for well_revoke_device; never show that id to the user. Name a device by its name when it has one, else by its kind, and say when Well last saw it.

Only the user's own devices are listed; another member's devices are never visible. An empty list means the user paired no device.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

Name	Required	Description
`workspace_id`	No	Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
`conversation_id`	No	The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
`workspace_scope`	No	Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

Name	Required	Description
`error`	No
`devices`	No	The user's own paired devices, the most recently seen first. Absent on failure.
`success`	Yes
`conversation_id`	No	The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
`newly_connected`	No	Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
`resolved_workspace`	No	The workspace that answered, when the caller named none and the token authorizes several.
`conversation_id_note`	No	Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.
`conversation_id_source`	No	Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 28, 2026
- removedOutput schema / properties / devices / items / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / devices / items / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / resolved_workspace / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / resolved_workspace / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedOct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, yet the description still adds substantial behavioral context: only the user's own devices are visible, an empty list is a meaningful answer, and the device_id must never be surfaced to the user. That privacy/display rule is exactly the kind of trait annotations cannot express.

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?

Front-loaded with the purpose and then the invocation rules, and nearly every sentence carries distinct information. Slight redundancy between the opening 'Use this when the person asks to list paired devices' and the later enumerated triggers, but overall it is tight for the amount of ground it covers.

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?

Output schema covers return values, annotations cover the safety profile, and the description fills in the remaining gaps an agent needs: how to render a device to the user, what to do with device_id, how to interpret an empty result, and the workspace-selection behavior. Nothing material 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?

Schema coverage is 100%, so the baseline is 3. The description still contributes operational meaning beyond the schema by explaining the multi-workspace decision ('When the token authorizes several, this read will not guess which one you mean: pass workspace_id') and that no prior workspace call is needed in the single-workspace case, though it does not touch conversation_id or workspace_scope.

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 ('List the user's own paired devices') and immediately defines what a paired device actually is (a computer whose browser, with the Well extension, was paired via a WhatsApp code). This is far more than a restatement of the name and separates it cleanly from the write-side sibling well_revoke_device.

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 explicit triggers ('quels appareils sont appairés ?', 'show my paired devices'), a sequencing rule ('always before well_revoke_device, to find the id of the device to unpair'), and workspace-token conditions. Both when-to-use and the dependency on the sibling are spelled out, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Well 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?