Skip to main content
Glama
Sign In

Well

by io.github.WellApp-ai
OverviewDiscussionsAdmin

Get a booking page

well_get_booking_page
Read-onlyIdempotent

Read one booking page the user owns, with its settings and link. Call this when the user asks about one booking page they named, and the id comes from a list result.

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.
booking_page_idYesThe id of the booking page, from a list result.
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
pageNo
errorNo
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 / page / properties / calendar_view
      Added value: +{
+  "enum": [
+    "month",
+    "two_weeks"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / page / properties / theme
      Added value: +{
+  "enum": [
+    "dark",
+    "light"
+  ],
+  "type": "string"
+}
    • removedOutput schema / properties / page / properties / weekdays
      Removed value: -{
-  "items": {
-    "type": "number"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / page / 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 / page / properties / window_end
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / page / properties / window_start
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / page / 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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds behavior beyond that: the read is ownership-scoped ("the user owns") and returns settings plus the link, which tells the agent it is not a bare metadata fetch.

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 padding, with the resource and scope front-loaded and the usage condition second. Every clause carries information the agent needs.

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 spelled out, and all four parameters are documented. The remaining gap is sibling disambiguation against well_get_booking_page_draft, well_update_booking_page and well_delete_booking_page, which the description never addresses.

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 coverage is 100%, so the workspace_id, workspace_scope and conversation_id semantics are fully documented in the schema. The only added meaning is "the id comes from a list result," which largely restates the booking_page_id field description; baseline 3 applies.

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?

"Read one booking page the user owns, with its settings and link" gives a specific verb (read), a single-resource scope, and the payload shape. It does not distinguish this from the sibling well_get_booking_page_draft, which an agent could easily confuse with this published-page read, so it stops short of 5.

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?

It states the triggering condition ("when the user asks about one booking page they named") and the prerequisite that the id comes from a list result, which implies well_list_booking_pages as the feeder. No explicit when-not or named alternative (e.g. the draft variant) is given.

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