Well

Get design tokens

well_get_design_tokens

Read-only

Get Well's colours, shape and type vocabulary, so a view you compose for Well data looks like Well rather than a generic page.

Call this ONLY when you are about to render something yourself — an HTML artifact, a report, a chart you are drawing. You do not need it to answer in prose or in a markdown table.

Do NOT use it to restyle a card a Well tool already drew. Where a tool ships its own card the host renders it, and a second styled copy of the same figures is a duplicate, not an improvement.

Returns colors (roles, not raw token names — page_background, card_surface, text_primary, accent, positive, negative, ...), series (categorical chart colours in the order to consume them), shape (corner radius and gap), fonts, and color_scheme, which tells you which ground to compose against. When it is absent the stylesheet did not declare one — pick a ground from page_background rather than assuming.

Values come from the same token package the Well app, the browser extension and the tool cards compile against, so they cannot drift from the product.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`workspace_id`	No	Target workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
`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.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`fonts`	Yes
`hints`	No
`shape`	Yes
`colors`	Yes
`series`	Yes
`success`	Yes
`color_scheme`	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.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id

Added value: +{
+  "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"
+}

addedOutput schema / properties / conversation_id_note

Added value: +{
+  "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id_source

Added value: +{
+  "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"
+}

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / workspace_id / description

Previous value: -"Target workspace. Omit to use the only authorized workspace, or (for read tools) to query all authorized workspaces grouped by workspace. Required for write tools when the token authorizes more than one workspace."New value: +"Target workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer."

AddedAug 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds valuable behavioral context: it describes the return object's structure (colors, series, shape, fonts, color_scheme), explains how to interpret the absence of color_scheme, and notes that values come from the token package and cannot drift. It also clarifies that omitting workspace_id returns the same answer, which is a behavioral nuance beyond the schema. No contradictions with annotations.

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?

The description is moderately long but every sentence earns its place. It front-loads the core purpose and then delivers usage constraints, return-value semantics, and a final note on provenance. While it could be trimmed slightly (e.g., the last sentence on token drift is somewhat tangential), it remains well-structured and efficient without redundancy.

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 read-only tool with two optional parameters and a rich return object, the description is complete. It explains when to use it, when not to, what the return object contains and how to interpret it, and covers the edge case of missing color_scheme. The presence of an output schema reduces the need to detail return formats, and the description provides the semantic guidance needed for correct invocation. Nothing critical is missing.

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 100%, so both parameters are fully documented in the schema. The description adds one meaningful clarification beyond the schema: it explicitly states that omitting workspace_id returns the same answer because tokens describe the package, not workspace data. This is valuable extra semantic info, so a score of 4 is justified over the baseline 3.

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 clearly states the tool's purpose: 'Get Well's colours, shape and type vocabulary' with the explicit goal of making composed views look like Well. It distinguishes itself from all siblings by being the only tool about design tokens, and it specifies the exact resource (colours, shape, type) with a concrete verb 'Get'.

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?

Usage guidance is explicit and comprehensive. It states the condition 'Call this ONLY when you are about to render something yourself' and provides clear exclusions: 'You do not need it to answer in prose or in a markdown table' and 'Do NOT use it to restyle a card a Well tool already drew.' It also references the alternative (host-rendered cards) and explains why a second styled copy is a duplicate. This is model guidance.

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?