Well

Get vault item

well_get_vault_item

Read-only

Read one of the user's own vault items by its vault_item_id, from well_list_vault_items: its category, its site and user name for a login, and when Well last used it. Call it when the user asks about one saved login you already listed ("quand as-tu utilisé mon identifiant Amazon ?").

The result never holds a password or any other secret, and no tool reveals one. Never show the id to the user. A refusal means no item of the user has that id: list the items again, never guess an id.

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.
`vault_item_id`	Yes	The vault_item_id of one item, from well_list_vault_items.
`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
`item`	No	The item's overview, never its secret. Absent on failure.
`error`	No
`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.

Changed1 schema field changedNov 3, 2026

changedOutput schema / properties / item / properties / last_use_outcome / anyOf

Previous value: -[
-  {
-    "enum": [
-      "ok",
-      "refused_not_owner",
-      "refused_endpoint",
-      "refused_deleted",
-      "refused_origin",
-      "key_service_unavailable",
-      "key_mismatch",
-      "login_refused"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "ok",
+      "refused_not_owner",
+      "refused_endpoint",
+      "refused_deleted",
+      "refused_origin",
+      "key_service_unavailable",
+      "key_mismatch",
+      "login_refused",
+      "refused_suspended",
+      "refused_no_sign_in_notice"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint false, but the description adds substantial context they cannot carry: the result never contains a password or other secret, the id must never be shown to the user, and a refusal has a defined recovery (re-list, never guess). The single-workspace vs multi-workspace rule ('this read will not guess which one you mean') further explains runtime behavior.

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?

Three short paragraphs, front-loaded with the verb, the id source, and the trigger condition, followed by safety and workspace rules. Slight redundancy with the schema on the workspace_id rule keeps it from being maximally tight, but no sentence is wasted.

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?

No output schema gap to fill and the description covers what matters for correct invocation: id provenance, secret-free results, refusal handling, and workspace scoping. An agent has everything needed to call it correctly and interpret a failure.

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 both workspace_id and vault_item_id are already documented in the schema, including the omit-when-one-workspace rule. The description restates the workspace rule with added emphasis ('will not guess') but adds no new syntax or format detail beyond the 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 — read one vault item by its vault_item_id — and names the sibling that supplies the id (well_list_vault_items), plus what the result contains (category, site, user name, last-used time). An agent can distinguish this from well_list_vault_items and well_delete_vault_item without opening a 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?

Explicit when-to-use with a concrete user phrasing example, an explicit prerequisite (an item already listed), and an explicit failure path: a refusal means no item has that id, so list again rather than guess. It also states the workspace condition that decides whether the call can be made directly or needs workspace_id.

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?