Skip to main content
Glama
Sign In
zygiu-zygis

basecoat-ui

by zygiu-zygis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_design_context

Read-onlyIdempotent

Read a focused design view from Basecoat UI sessions—overview, decisions, graph, rules, focus, or next—by design ID, with optional revision pinning. Does not create sessions.

Instructions

Read a focused design view: sessions (no designId), overview, decisions, graph, rules, focus, or next. Pin revision on first read; continuations must match. Does not create sessions.

Input Schema

NameRequiredDescriptionDefault
idNoAlternative design session ID alias matching designId.
nameNoAlternative design session ID alias matching designId.
viewNoContext perspective to retrieve: "sessions", "overview", "decisions", "graph", "rules", "focus", or "next". Defaults to "sessions".
cursorNoPagination cursor for paginated context listings.
nodeIdNoTarget node ID within the page (for "node" view).
pageIdNoTarget page ID within the design session (for "page" or "node" view).
designIdNoTarget design session ID (required for all views except "sessions").
revisionNoTarget design session revision to inspect (defaults to latest).
componentIdNoAlternative design session ID alias matching designId.
environmentNoTarget environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.8.0
    • addedInput schema / properties / componentId
      Added value: +{
+  "description": "Alternative design session ID alias matching designId.",
+  "maxLength": 64,
+  "type": "string"
+}
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor for paginated context listings."
    • addedInput schema / properties / designId / description
      Added value: +"Target design session ID (required for all views except \"sessions\")."
    • addedInput schema / properties / environment
      Added value: +{
+  "description": "Target environment.",
+  "enum": [
+    "html",
+    "astro",
+    "react",
+    "vue",
+    "svelte"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Alternative design session ID alias matching designId.",
+  "maxLength": 64,
+  "type": "string"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Alternative design session ID alias matching designId.",
+  "maxLength": 64,
+  "type": "string"
+}
    • addedInput schema / properties / nodeId / description
      Added value: +"Target node ID within the page (for \"node\" view)."
    • addedInput schema / properties / pageId / description
      Added value: +"Target page ID within the design session (for \"page\" or \"node\" view)."
    • addedInput schema / properties / revision / description
      Added value: +"Target design session revision to inspect (defaults to latest)."
    • addedInput schema / properties / view / description
      Added value: +"Context perspective to retrieve: \"sessions\", \"overview\", \"decisions\", \"graph\", \"rules\", \"focus\", or \"next\". Defaults to \"sessions\"."
    • removedInput schema / required
      Removed value: -[
-  "view"
-]
  2. Addedv1.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive, so the bar is lower. The description still adds real value beyond them with the revision-pinning contract ("Pin revision on first read; continuations must match"), a stateful constraint not expressed anywhere in annotations or schema.

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?

Two dense sentences with no padding, front-loaded on the enumerated views. It is efficient but slightly cryptic — the second sentence's contract is terse enough to require re-reading, which keeps it just short of ideal.

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?

For a 10-parameter read tool with no output schema, the definition covers the view set and revision semantics but says nothing about cursor/pagination behavior or how the views differ in payload. The individual schema descriptions carry most of the parameter burden, so it is adequate but leaves notable gaps.

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 the baseline is 3 and the schema already documents all ten parameters including the view enum and designId requirement. The description nonetheless adds the non-schema revision-continuation rule and notes the designId exemption for the sessions view, giving marginal extra meaning.

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 ("Read") plus the resource (a focused design view) and enumerates the seven valid views, so the agent knows exactly what is retrieved. It also carves out scope against a sibling with "Does not create sessions," implicitly separating it from begin_design, though it doesn't name that 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 Guidelines3/5

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

It gives conditional guidance ("sessions (no designId)") and a revision-continuation rule, which is more than nothing. However, it never states when to prefer one view over another or names the alternative tool an agent should pick for session creation, so usage is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools