Skip to main content
Glama
Sign In

Well

by io.github.WellApp-ai
OverviewDiscussionsAdmin

Retired: use well_update_task

well_update_browser_hand_off_run
Read-only

Retired, runs nothing. Call well_update_task with the task_id of the browser task and status "cancelled". well_list_tasks with task_kind "browser-task" finds the task_id.

Input Schema

NameRequiredDescriptionDefault
conversation_idNoThe 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • removedInput schema / properties / browser_hand_off_run_id
      Removed value: -{
-  "description": "The run to stop. Leave it out on WhatsApp to stop every run handed off from the conversation.",
-  "format": "uuid",
-  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-  "type": "string"
-}
    • removedInput schema / properties / idempotency_key
      Removed value: -{
-  "description": "Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.",
-  "maxLength": 255,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / status
      Removed value: -{
-  "description": "Always \"stopped\": stopping is the only change.",
-  "enum": [
-    "stopped"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / workspace_id
      Removed value: -{
-  "description": "Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.",
-  "format": "uuid",
-  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-  "type": "string"
-}
    • removedInput schema / properties / workspace_scope
      Removed value: -{
-  "description": "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.",
-  "enum": [
-    "family"
-  ],
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "status"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "conversation_id": {
-      "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
-      "type": "string"
-    },
-    "conversation_id_note": {
-      "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
-      "type": "string"
-    },
-    "conversation_id_source": {
-      "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
-      "enum": [
-        "host_meta",
-        "argument",
-        "minted"
-      ],
-      "type": "string"
-    },
-    "error": {
-      "type": "string"
-    },
-    "message": {
-      "type": "string"
-    },
-    "newly_connected": {
-      "description": "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.",
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "name": {
-            "type": "string"
-          },
-          "service_id": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "name",
-          "service_id"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "outcome": {
-      "enum": [
-        "stopped",
-        "already_stopped",
-        "no_run",
-        "already_ended",
-        "failed"
-      ],
-      "type": "string"
-    },
-    "stop_line_sent": {
-      "type": "boolean"
-    },
-    "stopped_tasks": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "success": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "success"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • addedOutput schema / properties / stop_line_sent
      Added value: +{
+  "type": "boolean"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, consistent with a no-op. The description adds the critical behavioral fact beyond annotations: the tool is retired and performs no work, preventing wasted calls. It does not discuss the accepted conversation_id, but for a retired tool that omission is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two short sentences, front-loaded with the retirement notice and followed by actionable redirection. Every sentence earns its place by either preventing a useless call or routing to the correct tool.

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?

For a retired no-op with annotations and no output schema, the description is complete: it states that nothing runs and gives exact replacement calls. An agent needs no further information to avoid or redirect this tool correctly.

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 the single optional conversation_id parameter is already fully documented in the schema. The description adds no parameter-level detail, which is appropriate given the tool runs nothing, so the baseline score of 3 applies.

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?

The description immediately states the tool is retired and 'runs nothing', which is a specific and unambiguous purpose. It then names the replacement tools, so an agent can distinguish this no-op from real browser-task operations among many siblings.

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?

It gives explicit operational guidance: call well_update_task with the task_id and status "cancelled", and use well_list_tasks with task_kind "browser-task" to find the task_id. This tells the agent both the alternative and how to obtain the required identifier.

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

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