Skip to main content
Glama
Sign In

Well

by io.github.WellApp-ai
OverviewDiscussionsAdmin

Retired: use well_create_browser_task

well_create_portal_fetch
Read-only

Retired, runs nothing. Call well_create_browser_task with executor_type "system" and a browser block whose goal_kind is "portal_fetch", with the same suppliers.

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 / 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 / run_in_background
      Removed value: -{
-  "const": true,
-  "description": "Always true: the person's own message explicitly asked to fetch these receipts as a background task. Without that ask, do not call this tool.",
-  "type": "boolean"
-}
    • removedInput schema / properties / suppliers
      Removed value: -{
-  "description": "The picked portal leads of this workspace, at most 5.",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "company_id": {
-        "description": "The row's `company_id` in well_list_missing_invoices.",
-        "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"
-      },
-      "transaction_ids": {
-        "description": "The `id` of each of the row's `transactions`, at most 10.",
-        "items": {
-          "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"
-        },
-        "maxItems": 10,
-        "minItems": 1,
-        "type": "array"
-      }
-    },
-    "required": [
-      "company_id",
-      "transaction_ids"
-    ],
-    "type": "object"
-  },
-  "maxItems": 5,
-  "minItems": 1,
-  "type": "array"
-}
    • 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: -[
-  "suppliers",
-  "run_in_background"
-]
    • 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"
-    },
-    "error_reason": {
-      "enum": [
-        "no_workspace",
-        "inactive_workspace",
-        "no_person",
-        "not_from_whatsapp",
-        "no_cloud_browser",
-        "unknown_company",
-        "unknown_transaction",
-        "not_of_supplier",
-        "no_portal",
-        "too_many_payments",
-        "nothing_missing",
-        "run_active",
-        "rate_limited",
-        "failed"
-      ],
-      "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"
-    },
-    "resolved_workspace": {
-      "additionalProperties": false,
-      "description": "The workspace that answered, when the caller named none and the token authorizes several.",
-      "properties": {
-        "name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "workspace_id": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "workspace_id",
-        "name"
-      ],
-      "type": "object"
-    },
-    "runner": {
-      "enum": [
-        "paired_chrome",
-        "cloud"
-      ],
-      "type": "string"
-    },
-    "skipped_transaction_ids": {
-      "description": "Payments left out: they already have a document, or carry no amount or date.",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "success": {
-      "type": "boolean"
-    },
-    "suppliers": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "company_id": {
-            "type": "string"
-          },
-          "login": {
-            "enum": [
-              "saved",
-              "no_saved_login",
-              "login_not_chosen"
-            ],
-            "type": "string"
-          },
-          "payments": {
-            "maximum": 9007199254740991,
-            "minimum": -9007199254740991,
-            "type": "integer"
-          },
-          "site": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "company_id",
-          "site",
-          "login",
-          "payments"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "success"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and the description reinforces and extends this with the crucial fact that the tool executes nothing at all, which no annotation can express. It stops short of saying whether a call returns an error or an empty result, which is the one behavioral detail an agent might still wonder about.

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 clauses with the critical fact ("Retired, runs nothing") front-loaded before the migration instructions. Every word carries weight; nothing is repeated from the title alone.

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 one-optional-parameter retired shim with no output schema, the description supplies everything needed to avoid calling it and to make the correct replacement call. The only missing piece is the exact outcome of invoking it anyway (error versus silent no-op), a minor gap for a deprecated tool.

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% and the single conversation_id parameter is thoroughly documented there, so the description adds no param-level meaning. The phrase "with the same suppliers" describes the replacement tool's arguments rather than this tool's schema, which is slightly ambiguous since no suppliers parameter exists here. Baseline 3 is appropriate given the schema does all the work.

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?

"Retired, runs nothing" immediately establishes that this is a no-op shim rather than a functional tool, and the follow-up names the successor along with the exact configuration that replaces it (executor_type "system", goal_kind "portal_fetch"). It distinguishes itself from the huge sibling list by routing to one specific sibling, though it never states what the original portal fetch actually did, so an agent must infer the semantics from the replacement call.

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?

The description explicitly tells the agent not to use this tool and gives a fully specified alternative: call well_create_browser_task with executor_type "system" and a browser block whose goal_kind is "portal_fetch", reusing the same suppliers. There is no ambiguity about which path to take.

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