Well

Create workspace view

well_create_workspace_view

Save one records view with its root, name, columns, filters, sort and layout, for example to keep a list the person was shown as a named view. Read the root's field schema first. This saves a reusable view without changing its source records. Use well_list_views to find existing views; set auto_group false to keep the grouping exactly as supplied.

Input Schema

Name	Required	Description
`name`	Yes
`root`	Yes
`sort`	No
`columns`	No
`filters`	No
`group_by`	No
`auto_group`	No
`layout_type`	No
`workspace_id`	No	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.
`layout_config`	No
`display_fields`	No
`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.
`idempotency_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
`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
`code`	No
`name`	No
`error`	No
`success`	Yes
`view_id`	No
`reply_lines`	No
`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.
`near_candidates`	No
`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.
`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.
`near_candidates_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / root / enum

Previous value: -[
-  "companies",
-  "people",
-  "connectors",
-  "workspaces",
-  "workspace_connectors",
-  "invoices",
-  "documents",
-  "notes",
-  "transactions",
-  "accounts",
-  "memberships",
-  "payment_means",
-  "invoice_payment_means",
-  "cards",
-  "checks",
-  "chat_conversations",
-  "ledger_accounts",
-  "journals",
-  "journal_entries",
-  "tax_rates",
-  "exchange_rates",
-  "invoice_transactions",
-  "media",
-  "emails",
-  "phones",
-  "web_links",
-  "locations",
-  "categories",
-  "invoice_items",
-  "account_balances",
-  "tasks",
-  "workspace_connector_sync_logs",
-  "blueprint_runs",
-  "billing_events",
-  "payslips",
-  "messages",
-  "calendars",
-  "calendar_events",
-  "projects",
-  "shipments",
-  "activities",
-  "company_relations",
-  "connector_filters",
-  "employment_contracts",
-  "field_definitions",
-  "payslip_line_rubrics",
-  "subscriptions",
-  "supplier_payment_terms",
-  "workspace_category_overrides",
-  "workspace_groups",
-  "products",
-  "inventories",
-  "inventory_movements",
-  "allocations",
-  "project_changes",
-  "shipment_events",
-  "statutory_values",
-  "adoption_scopes",
-  "browser_skills",
-  "canvas_views",
-  "connector_requests",
-  "document_layouts",
-  "expense_notes",
-  "field_rules",
-  "flow_runs",
-  "memory_units",
-  "share_links",
-  "skills",
-  "transaction_category_rules",
-  "workspace_posting_mappings",
-  "workspace_schedules",
-  "workspace_views"
-]New value: +[
+  "companies",
+  "people",
+  "connectors",
+  "workspaces",
+  "workspace_connectors",
+  "invoices",
+  "documents",
+  "notes",
+  "transactions",
+  "accounts",
+  "memberships",
+  "payment_means",
+  "invoice_payment_means",
+  "cards",
+  "checks",
+  "chat_conversations",
+  "ledger_accounts",
+  "journals",
+  "journal_entries",
+  "tax_rates",
+  "exchange_rates",
+  "invoice_transactions",
+  "media",
+  "emails",
+  "phones",
+  "web_links",
+  "locations",
+  "categories",
+  "invoice_items",
+  "account_balances",
+  "tasks",
+  "workspace_connector_sync_logs",
+  "blueprint_runs",
+  "billing_events",
+  "payslips",
+  "messages",
+  "calendars",
+  "calendar_events",
+  "projects",
+  "shipments",
+  "activities",
+  "company_relations",
+  "connector_filters",
+  "employment_contracts",
+  "field_definitions",
+  "payslip_line_rubrics",
+  "subscriptions",
+  "supplier_payment_terms",
+  "workspace_category_overrides",
+  "workspace_groups",
+  "products",
+  "inventories",
+  "inventory_movements",
+  "daily_metrics",
+  "allocations",
+  "project_changes",
+  "shipment_events",
+  "statutory_values",
+  "adoption_scopes",
+  "browser_skills",
+  "canvas_views",
+  "connector_requests",
+  "document_layouts",
+  "expense_notes",
+  "field_rules",
+  "flow_runs",
+  "memory_units",
+  "share_links",
+  "skills",
+  "transaction_category_rules",
+  "workspace_posting_mappings",
+  "workspace_schedules",
+  "workspace_views"
+]

Changed3 schema fields changedNov 1, 2026

addedInput schema / properties / root / enum

Added value: +[
+  "companies",
+  "people",
+  "connectors",
+  "workspaces",
+  "workspace_connectors",
+  "invoices",
+  "documents",
+  "notes",
+  "transactions",
+  "accounts",
+  "memberships",
+  "payment_means",
+  "invoice_payment_means",
+  "cards",
+  "checks",
+  "chat_conversations",
+  "ledger_accounts",
+  "journals",
+  "journal_entries",
+  "tax_rates",
+  "exchange_rates",
+  "invoice_transactions",
+  "media",
+  "emails",
+  "phones",
+  "web_links",
+  "locations",
+  "categories",
+  "invoice_items",
+  "account_balances",
+  "tasks",
+  "workspace_connector_sync_logs",
+  "blueprint_runs",
+  "billing_events",
+  "payslips",
+  "messages",
+  "calendars",
+  "calendar_events",
+  "projects",
+  "shipments",
+  "activities",
+  "company_relations",
+  "connector_filters",
+  "employment_contracts",
+  "field_definitions",
+  "payslip_line_rubrics",
+  "subscriptions",
+  "supplier_payment_terms",
+  "workspace_category_overrides",
+  "workspace_groups",
+  "products",
+  "inventories",
+  "inventory_movements",
+  "allocations",
+  "project_changes",
+  "shipment_events",
+  "statutory_values",
+  "adoption_scopes",
+  "browser_skills",
+  "canvas_views",
+  "connector_requests",
+  "document_layouts",
+  "expense_notes",
+  "field_rules",
+  "flow_runs",
+  "memory_units",
+  "share_links",
+  "skills",
+  "transaction_category_rules",
+  "workspace_posting_mappings",
+  "workspace_schedules",
+  "workspace_views"
+]

removedInput schema / properties / root / maxLength
```
Removed value: -100
```
removedInput schema / properties / root / minLength
```
Removed value: -1
```

Changed4 schema fields changedOct 28, 2026

addedOutput schema / properties / code
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / near_candidates

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "company_id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "company_id",
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / near_candidates_truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / reply_lines

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed2 schema fields changedOct 23, 2026

removedInput schema / properties / creator_kind

Removed value: -{
-  "enum": [
-    "person",
-    "assistant"
-  ],
-  "type": "string"
-}

changedInput schema / properties / layout_type / enum

Previous value: -[
-  "table",
-  "kanban",
-  "calendar",
-  "gallery",
-  "chart",
-  "list",
-  "graph"
-]New value: +[
+  "table",
+  "kanban",
+  "calendar",
+  "gallery",
+  "chart",
+  "list",
+  "graph",
+  "timeline"
+]

AddedOct 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description adds real value on top by scoping the write's blast radius: it saves a reusable view 'without changing its source records'. It also discloses the auto_group behavioral knob and a schema-read prerequisite. It does not mention authorization or workspace-resolution behavior, though workspace_id and workspace_scope carry that in their own schema descriptions.

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?

Four sentences, front-loaded with the payload shape, then prerequisites, then the non-destructive guarantee, then routing. Every sentence carries information, though the parenthetical example ('for example to keep a list the person was shown as a named view') is slightly wordy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 parameters including several nested object arrays and only 29% schema coverage, the description covers the primary fields and the prerequisite but leaves display_fields (roles, displayType, skill render hints) and layout_config entirely undocumented anywhere. It is adequate to start the call correctly, not adequate to use the tool fully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 29%, so the description must compensate, and it does for the core payload: it names root, name, columns, filters, sort and layout, and explains auto_group's semantics ('set auto_group false to keep the grouping exactly as supplied') beyond the bare boolean. The complex nested display_fields array and group_by's null-vs-array behavior get no description-side explanation.

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?

The description states a specific verb and resource ('Save one records view') and enumerates exactly what the view captures (root, name, columns, filters, sort, layout), so the agent knows what is being persisted. It clearly separates itself from the read-side sibling by naming well_list_views, but does not distinguish itself from well_update_workspace_view or well_delete_workspace_view, leaving create-vs-update inference to the tool name.

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 gives a concrete trigger (keep a list the person was shown as a named view), a prerequisite ('Read the root's field schema first'), and a routing rule ('Use well_list_views to find existing views'). What is missing is an explicit exclusion: nothing says when to prefer well_update_workspace_view over creating a duplicate view.

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?