Skip to main content
Glama
Sign In

Well

by io.github.WellApp-ai
OverviewDiscussionsAdmin

List booking pages

well_list_booking_pages
Read-onlyIdempotent

List the user's booking pages with each page's link, the main page first. Call this when the user asks for their booking link or their booking pages, including when they ask to send their booking link.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget 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_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.
workspace_scopeNoRestrict 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

NameRequiredDescriptionDefault
errorNo
pagesNo
messageYes
successYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools 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_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere 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.

  1. Changed7 schema fields changed
    • addedOutput schema / properties / pages / items / properties / calendar_view
      Added value: +{
+  "enum": [
+    "month",
+    "two_weeks"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / pages / items / properties / theme
      Added value: +{
+  "enum": [
+    "dark",
+    "light"
+  ],
+  "type": "string"
+}
    • removedOutput schema / properties / pages / items / properties / weekdays
      Removed value: -{
-  "items": {
-    "type": "number"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / pages / items / properties / weekly_hours
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "days": {
+        "items": {
+          "type": "number"
+        },
+        "type": "array"
+      },
+      "end": {
+        "type": "string"
+      },
+      "start": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "days",
+      "start",
+      "end"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / pages / items / properties / window_end
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / pages / items / properties / window_start
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / pages / items / required
      Previous value: -[
-  "booking_page_id",
-  "slug",
-  "title",
-  "description",
-  "duration_minutes",
-  "primary_color",
-  "location",
-  "weekdays",
-  "window_start",
-  "window_end",
-  "is_default",
-  "link",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "booking_page_id",
+  "slug",
+  "title",
+  "description",
+  "duration_minutes",
+  "primary_color",
+  "calendar_view",
+  "theme",
+  "location",
+  "weekly_hours",
+  "is_default",
+  "link",
+  "created_at",
+  "updated_at"
+]
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the ordering guarantee that the main page comes first, which is genuinely useful behavior, but says nothing about how many pages come back, what happens with zero pages, or how the link is formatted.

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 sentences, zero waste. The output shape is front-loaded and the invocation guidance follows, with no redundant restatement of the title.

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?

An output schema exists, so return values need not be explained, and the input schema fully documents all three optional parameters. For a simple read-only list tool this is essentially complete, with only the empty-result and multi-page edge cases left unstated.

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 schema itself explains workspace_id, conversation_id and workspace_scope in detail. The description adds no parameter-level meaning at all, so the baseline 3 applies rather than anything higher.

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?

States a specific verb and resource ('List the user's booking pages') and adds what each entry contains (the page link) plus the ordering rule ('main page first'). This distinguishes it from well_get_booking_page and well_create_booking_page by implication, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit triggering conditions: the user asks for their booking link or booking pages, including the send-my-link phrasing. It does not cover exclusions or point to the single-page alternative (well_get_booking_page) when the user asks about one specific page, which keeps it short of a 5.

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