figjam-context-mcp
Turns FigJam/Figma boards into locally cached, source-cited context for LLMs.
Ingest boards with
ingest_board: read via the Figma REST API, cluster stickies/tables/images/arrows, save a local snapshot, and optionally prioritize image interpretation withfocusNodeIds.Read context with
get_board_context: get overviews and section summaries, search by topic, read specific nodes/sections/tables or outside-section content, paginate, and retrieve full excerpts with Figma links.Answer specific questions with
answer_from_board: return an answer with validated node-level citations or an insufficient-evidence result.Track changes with
diff_board: compare retained snapshots to see cluster, node, table-cell, and connector changes.Check model setup with
diagnose_llm_config: test configured text/vision models using small synthetic checks.Use optional LLM/vision providers for interpretation and answers;
max_speedavoids provider calls, and snapshots stay in a private local cache with credential redaction.
Provides tools to ingest FigJam boards, retrieve context summaries and clusters, and answer questions about board content.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@figjam-context-mcpWhat are the main action items from the FigJam board?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
figjam-context-mcp
A local MCP server that turns FigJam boards into source-cited context for LLMs. It reads a board through the Figma REST API, groups stickies, tables, images and arrows into clusters, and answers questions with links back to the original nodes.

Rendered from the tool calls and outputs of a real run against the public
demo board with
figjam-context-mcp 0.10.2 and openai/gpt-4.1-mini. Figma's MCP server
(use_figma) made the edit.
Why
Workshop boards hold research notes, decisions and open questions, but an LLM cannot read a canvas. Screenshots and PDF exports lose tables, arrow direction and the link to the source. This server keeps the board's structure and cites every answer to the nodes it came from.
Related MCP server: Miro MCP Server
Compared with Figma's MCP server
Figma's official MCP server reads a FigJam board or node with its images
(get_figjam) and edits boards (use_figma). This server turns a workshop
board into context an assistant can cite and track:
large boards read section by section, with an overview, size-limited pages and search
source IDs in compact overviews, with Figma links in full excerpts and answer citations
tables read row by row
local snapshots, and
diff_boardto see what changedexplicit credentials redacted before they reach the cache, the output or a model
image descriptions from a vision model you configure
The two work together: in the demo above, Figma's server edits the board and this one reports the change.
Tools
Tool | What it does | LLM call |
| Reads a board, clusters it and saves a local snapshot. Re-ingests reuse unchanged clusters; | In |
| Reads saved context, automatically using compact source-ID lines for large section reads; | No |
| Answers one specific question (a number, status or decision) from the most relevant excerpts, with node-level citations or an insufficient-evidence result. Not meant for whole-board summaries. | Yes |
| Compares snapshots with bounded lists and full totals: clusters, nodes, table cells (0-based), arrows with source IDs, section/frame renames and layout counts. Notes unchanged re-ingests. | No |
| Tests the configured models with small text and image JSON checks. | Yes |
ingest_board also reads Figma design files (/design/, /file/ and /proto/
URLs), but clustering and reading order are made for FigJam boards.
Quick start
Five steps. Requires Node.js 22.12 or later. Step 4 sets the model provider that
answer_from_board, diagnose_llm_config and image interpretation need; it is optional.
Node.js. Check the installed version with
node --version; install Node.js 22.12 or later if it is older.Figma token. Create a personal access token under Settings → Security → Personal access tokens with the scope
file_content:read. The token's account must be able to open the board. Everyingest_boardcall is one Figma file download, a Tier 1 request. Figma allows View and Collab seats up to 20 Tier 1 requests a month on every plan, and says the actual limit may be lower (rate limits).Add the server with the example for your client below. The examples set only
FIGMA_ACCESS_TOKEN, so the server starts andingest_boardworks iningestMode: "max_speed"without a model provider.@latestwith--prefer-onlinemakes npx check the registry for the latest release on every start, even when package metadata is cached (npm configuration).Optional: model provider. Add
LLM_BASE_URLandLLM_API_KEYto the server'senvblock, then restart the client. Both are needed together; without them,balancedingests run text-only and say that the model settings are missing. Example with OpenRouter (create a key):LLM_BASE_URL=https://openrouter.ai/api/v1 LLM_API_KEY=your-openrouter-keyIn Claude Code, remove the entry with
claude mcp remove figjam-context(with the same--scopeas when you added it), then add it again with an--envflag for each variable (Claude Code). A local OpenAI-compatible server without sign-in still needsLLM_API_KEYset to any non-empty value. SetLLM_TEXT_MODELS,LLM_FAST_TEXT_MODELSandLLM_VISION_MODELSto its model names (configuration). Then rundiagnose_llm_configin step 5.Check the setup. Ask your assistant to ingest one of your boards with
ingestMode: "max_speed", for example "Ingest https://www.figma.com/board/FILE_KEY/Name with ingestMode max_speed." That makes one Figma request and no model call. A working setup answers with a line that startsIngested board FILE_KEY (snapshot …):and counts theclusters. Clients that show their tools, such as Claude Code with/mcp, list the server there (Claude Code). With a provider from step 4, also rundiagnose_llm_config; it checks the configured models with small synthetic inputs. For error messages, see common errors.
All settings: configuration.
Claude Code
claude mcp add --scope user --env FIGMA_ACCESS_TOKEN=your-figma-token --transport stdio figjam-context -- npx -y --prefer-online figjam-context-mcp@latest--scope user makes the server available in all your projects. Without it, Claude
Code stores the server for the current project only (scopes).
For longer ingests, set MCP_TOOL_TIMEOUT=300000 in the environment that launches
Claude Code and INGEST_BOARD_VISION_BUDGET_MS=270000 in the server environment,
leaving about 30 seconds for the rest of the ingest (Claude Code environment
variables).
Claude Desktop
Open Settings → Developer → Edit Config in Claude Desktop. This opens
claude_desktop_config.json; the file is at:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the server under mcpServers, keeping any other entries in the file:
{
"mcpServers": {
"figjam-context": {
"command": "npx",
"args": ["-y", "--prefer-online", "figjam-context-mcp@latest"],
"env": {
"FIGMA_ACCESS_TOKEN": "your-figma-token"
}
}
}
}Then quit Claude Desktop completely and start it again; the server starts with the app (MCP quickstart). The MCP documentation names no tool timeout setting for Claude Desktop, so keep the default image budget.
Codex CLI and ChatGPT desktop app
Add this to ~/.codex/config.toml; the app, CLI and IDE extension share this
configuration (OpenAI MCP setup):
[mcp_servers.figjam-context-mcp]
enabled = true
command = "npx"
args = ["-y", "--prefer-online", "figjam-context-mcp@latest"]
startup_timeout_sec = 30
default_tools_approval_mode = "approve"
[mcp_servers.figjam-context-mcp.env]
FIGMA_ACCESS_TOKEN = "your-figma-token"Without default_tools_approval_mode = "approve", ChatGPT may ask for approval
or abort tools with external effects; with it, the client never asks before board
content goes to the model provider, so use max_speed and avoid answer_from_board
for confidential boards.
For longer ingests, set tool_timeout_sec = 300 under
[mcp_servers.figjam-context-mcp] and INGEST_BOARD_VISION_BUDGET_MS = "270000" in its
env table, leaving about 30 seconds for the rest of the ingest (OpenAI timeout
options).
GitHub Copilot CLI
Add this to ~/.copilot/mcp-config.json
(Copilot CLI MCP setup):
{
"mcpServers": {
"figjam-context": {
"type": "local",
"command": "npx",
"args": ["-y", "--prefer-online", "figjam-context-mcp@latest"],
"env": {
"FIGMA_ACCESS_TOKEN": "your-figma-token"
},
"tools": ["*"]
}
}
}For longer ingests, set "timeout": 300000 on the server in
~/.copilot/mcp-config.json and "INGEST_BOARD_VISION_BUDGET_MS": "270000" in its
env, leaving about 30 seconds for the rest of the ingest (tested with a 600000 ms
timeout).
VS Code
In the Copilot harness, add the server under Global → Copilot Global in
Chat: Open Customizations (Command Palette), then MCP Servers. VS Code writes it to
~/.copilot/mcp-config.json, the same file as in the Copilot CLI section, in the portable
mcpServers format (VS Code MCP servers,
configuration reference):
{
"mcpServers": {
"figjam-context": {
"type": "local",
"command": "npx",
"args": ["-y", "--prefer-online", "figjam-context-mcp@latest"],
"env": {
"FIGMA_ACCESS_TOKEN": "your-figma-token"
},
"tools": ["*"]
}
}
}The portable format has no input variables, so the token is stored in this file. Keep that file in your user directory and out of any repository.
Local harness only: to keep the token out of the file, open MCP: Open User
Configuration and use an input marked "password": true. VS Code does not forward
servers that need inputs to Copilot harness sessions, so this works only in the Local
harness (VS Code MCP configuration):
{
"inputs": [
{
"type": "promptString",
"id": "figma-token",
"description": "Figma personal access token (file_content:read)",
"password": true
}
],
"servers": {
"figjam-context": {
"type": "stdio",
"command": "npx",
"args": ["-y", "--prefer-online", "figjam-context-mcp@latest"],
"env": {
"FIGMA_ACCESS_TOKEN": "${input:figma-token}"
}
}
}
}Do not put tokens in a .vscode/mcp.json in a repository; VS Code's documentation
says not to commit tokens or passwords.
In the Local harness, "envFile": "${workspaceFolder}/.env" on the server in mcp.json
loads an environment file; the portable format does not support envFile, and the
server does not load a working-directory .env itself.
For longer ingests, use the Local harness with a per-server "timeout": 300000 in
mcp.json and "INGEST_BOARD_VISION_BUDGET_MS": "270000" in its env (about 30
seconds below the timeout); #343135
reports that remote HTTP tool calls in the Copilot harness, the default in 1.142, ignore
that timeout and stop after about 180 seconds, while the Local harness honors it.
Other MCP clients
For clients that accept mcpServers, add this to their MCP configuration:
{
"mcpServers": {
"figjam-context": {
"command": "npx",
"args": ["-y", "--prefer-online", "figjam-context-mcp@latest"],
"env": {
"FIGMA_ACCESS_TOKEN": "your-figma-token"
}
}
}
}Where the client supports a configurable tool timeout, raise it to about 300 seconds
using its documented setting and set INGEST_BOARD_VISION_BUDGET_MS=270000 in the
server environment, about 30 seconds below it.
Cursor has no configurable timeout: its IDE allows about 60 minutes, while ACP/CLI calls
stop at 60 seconds even with progress, so keep the default image budget on that path
(Cursor
support).
Using the tools
Then ask your assistant to ingest a board URL, for example "Ingest
https://www.figma.com/board/FILE_KEY/Name and list the open questions."
The boardId of every later call is the file key from that URL, or the URL
itself; a URL with a node-id and without nodeIds, topic and
outsideSections makes get_board_context read that node. To summarize
a board, the assistant calls ingest_board, then get_board_context without
parameters, whose first page names the largest sections and includes a section
overview with IDs within the page's size limit, and then reads the largest sections
by passing their IDs as nodeIds. Several IDs in one call take turns in request
order, up to 50 per call. For a whole-board summary, pass all top-level section IDs
with maxChars: 24000, follow the cursor in the text with the same arguments, then
read outsideSections: true.
Large nodeIds reads automatically use short source-ID lines, grouped by section,
when the first full page would leave unread excerpts. limit applies only with
the full view; an overview ignores it even when supplied. Read complete text and
its Figma link with the same boardId and snapshotId, the line's ID in
nodeIds, and detail: "full". For a table row, use its table ID.
Everything that lies in no section, such as loose notes and tables, comes with
outsideSections: true.
Compact overviews show the Figma link pattern for their node IDs (URL-encode the ID)
and shorten each text to a shared 50–120-character prefix with …; the host writes
the summary. Topic searches, outsideSections, single leaf, table or cell IDs and
small containers always return the full view.
Inputs are read as hosts and users send them. A node ID in link form (5-87,
5%3A87, I5-87%3B1-2) or a Figma link of the same board with a node-id is
read as the ID it stands for (5:87) in nodeIds and focusNodeIds, and the
text says so once; an ID that exists in the snapshot is never changed, and a
link of another board is an error. A key that differs from a parameter only in
case, _ or - (ingest_mode, node_ids) ends the call with
"did you mean …" before anything is done; any other unknown key is ignored and
named, without its value, in the text and in ignoredArguments of
structuredContent. File keys are case-sensitive: an unknown boardId lists
the stored boards (at most 10, most recent first) and names a key that differs
only in case.
How it works

Read.
ingest_boarddownloads the board through the Figma REST API on every call.get_board_contextandanswer_from_boardread the saved snapshot without a new request.Normalize. Nodes become text, table cells, images and connectors, with their pages, sections and named enclosing frames and groups. Tables are read row by row: row and column come from the cell IDs, and each row becomes one excerpt.
Cluster. Nearby nodes are grouped by rotation-aware distance. Arrows between groups become directed relations. Clusters without a model label are named after their section, and an arrow appears in the context once one of its ends, or a section, frame or group around one, is on the page.
Interpret. In
balancedmode, clusters with an image, or drawings without any text, get a vision-model summary within a 40-second budget; text clusters, however short, keep their extracted text. A cluster starts only when the time left fits it; unfinished clusters continue on the next ingest. WithfocusNodeIds, the images of the given sections, frames or nodes come first. Inmax_quality, one ingest interprets only a few dozen clusters within the 40-second image budget (20–35 on a board with about 300 clusters, measured with 3 parallel requests); the next ingest continues, each costs a Tier 1 file download, andfocusNodeIdssets the order.Serve. The snapshot is saved to a private local cache. Search favors excerpts containing more of the question’s words.
get_board_contextsearches it (BM25 over original text, table rows and names, arrow labels and table headings),answer_from_boardanswers with citations anddiff_boardcompares snapshots. Topic and question searches match whole words ignoring case and accents (words of five or more letters also match compounds that begin with them), but not other word forms, synonyms or translations. Use the board's words and language; an empty search does not prove the board lacks the topic. Paging, overviews and thedetailsetting are described in Using the tools. Full-view excerpt text is quoted with>on every line, and model-generated cluster labels are marked as model labels. Textcontentis the readable page;structuredContentholds each excerpt once, inoverview.text(with emptyevidenceandclusters) or inevidencefor the full view. Full excerpts inheritsnapshotIdfrom the response; absentchunkIndexmeans 0 and absenttruncatedormodelDerivedmeans false, with no inheritance of these flags from a cluster. Named frames and groups appear inframeNameson clusters and on excerpts whose location differs; their names also participate in search.
Models and cost
The default preset student-free uses free OpenRouter models: text and images go
to openrouter/free, which picks a free model that supports structured outputs
(and images, for images). The free default is best effort: free models change, hit rate limits
and time out. A request to openrouter/free or openrouter/auto that fails with
a provider error is sent once more, since the router may pick another model. Images go to the model with at most 1,024 px on the longest side;
larger ones are scaled down locally.
OpenRouter allows free models 20 requests per minute and 50 requests per day, or 1,000 per day once you have bought at least 10 credits (limits).
Figma limits requests by seat and plan (rate limits). File downloads and image renders are Tier 1: Dev and Full seats on paid plans get 10–20 requests per minute, View and Collab seats and files in Starter plans at most 20 per month. Every
ingest_boardcall is one file download, so a View or Collab seat allows about 20 ingests a month. Images come from the image fills instead, Tier 2 with at least 5 requests per minute, in one request per ingest. Renders are left for drawings without an image and as a fallback for images without a usable original; renders of several clusters share requests of up to 18 nodes, so 30 image clusters without image fills need 2 render requests.max_speedneeds neither.LLM_BASE_URLtakes any OpenAI-compatible endpoint; for paid models, setLLM_TEXT_MODELS,LLM_FAST_TEXT_MODELSandLLM_VISION_MODELS, for example all three toopenai/gpt-4.1-mini(provider charges apply).Run
diagnose_llm_configafter every model change. It checks JSON replies and image understanding with synthetic inputs.
Privacy
The server reads from Figma and never changes a board.
Hidden elements and their descendants are skipped before extraction, image loading and provider requests.
balancedandmax_qualityingests send board text and images (originals or renders) to the configured LLM provider.answer_from_boardsends the question and selected excerpts.max_speedwithget_board_contextanddiff_boardsends nothing to an LLM provider.Snapshots stay in a private per-user cache on your machine. Delete the cache directory to remove them.
Explicit credentials such as
Passwort: …or API keys are redacted before they reach the cache, tool output or an LLM provider (FIGJAM_MCP_REDACT_CREDENTIALS). This is a safety net, not a guarantee: images are not redacted, so keep credentials off the board.Keep tokens in the client's environment. A token passed as a tool argument can appear in client logs.
Limitations
Image interpretation gets 40 seconds per ingest by default; large boards need several ingests to interpret every image cluster.
A client that cancels an ingest, for example after a 60-second timeout, gets no partial result.
Free models are best effort. Citations show where an answer comes from, not that its conclusion is right.
Search is lexical; synonyms without shared words do not match.
Local stdio only; no hosted or multi-user mode.
Measured results: evaluation.
Development
git clone https://github.com/ecestnrkl/figjam-mcp.git
cd figjam-mcp
npm ci
cp .env.example .env # optional: add tokens for local development
npm run check # typecheck, tests, build, package validation
npm run package:smoke # install the packed package and exercise all tools
npm run eval:retrieval # offline retrieval and diff evaluation
npx --prefer-online @modelcontextprotocol/inspector --config inspector.config.jsonnpm run dev and inspector.config.json explicitly load the repository's .env
with Node's --env-file-if-exists=.env; existing environment values win. For other
launch commands, configure the MCP client's env or set FIGJAM_MCP_ENV_FILE to
the absolute path of the file.
See CONTRIBUTING.md and the changelog.
License
MIT © 2026 ecestnrkl
Available Tools
5 toolsanswer_from_boardAnswer From BoardARead-only
Answer one specific question, such as a number, a status or a decision, from the most relevant excerpts of an ingested board, with validated source citations or an insufficient-evidence result. It finds excerpts by the question's words (whole words, ignoring case and accents (words of five or more letters also match compounds that begin with them); no other word forms, synonyms or translations), so ask with the board's words and language. Keep its citations (node ID and Figma link) with the statements they support. It reads only a handful of excerpts: not for summaries, lists, risks or next steps across several sections; read those with get_board_context. Sends the question and the selected excerpts to the configured LLM provider; calls may incur charges.
| Name | Required | Description | Default |
|---|---|---|---|
| boardId | Yes | The Figma file key returned by ingest_board, or the board URL | |
| question | Yes | ||
| snapshotId | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| answer | Yes | |
| citations | Yes | |
| snapshotId | Yes | |
| citedClusters | Yes | |
| ignoredArguments | No | Unknown input keys that were ignored; their values are not echoed. Absent when none |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations it discloses real operational traits: it reads only a handful of excerpts, sends the question and excerpts to a configured LLM provider, and calls may incur charges. It also states the possible failure outcome (insufficient evidence) and the obligation to keep citations attached to the statements they support.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The purpose is front-loaded in the first sentence and each subsequent sentence covers a distinct concern (matching behavior, citation handling, scope limits, cost). The heavy parenthetical nesting in the matching sentence slightly hurts scannability but no sentence is filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values need not be fully explained, and the description still flags citations and the insufficient-evidence outcome. The remaining gap is snapshotId and any indication of which snapshot is used by default, which matters for reproducibility of an idempotentHint=false tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 33% (only boardId is described), so the description must compensate, and it does for the key parameter: exact whole-word, case- and accent-insensitive matching, five-letter compounds, and no synonyms or translations. The snapshotId parameter is never mentioned, which leaves one of three parameters entirely undocumented outside the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: answer one question (number, status, decision) from the most relevant excerpts of an ingested board, returning validated citations or an insufficient-evidence result. This is clearly distinguishable from get_board_context, which is named explicitly for the broader reading case.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives both when-to-use and when-not-to-use: not for summaries, lists, risks or next steps across several sections, and routes those to get_board_context. It also tells the agent how to phrase the input (use the board's words and language), which is actionable guidance rather than inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
diagnose_llm_configDiagnose LLM ConfigARead-only
Test the configured text and vision models with three small synthetic JSON challenges. Sends synthetic text and an image to the configured provider, may incur charges, and reports semantic/schema failures. Does not read board contents. Use after changing model/provider settings.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| ok | Yes | |
| checks | Yes | |
| preset | Yes | |
| summary | Yes | |
| textModels | Yes | |
| visionModels | Yes | |
| fastTextModels | Yes | |
| ignoredArguments | No | Unknown input keys that were ignored; their values are not echoed. Absent when none |
| providerRequireParameters | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond the annotations by warning that it sends synthetic text and an image to the configured provider and may incur charges — cost exposure is exactly the kind of thing readOnlyHint/openWorldHint do not convey. Reports failures rather than throwing, which is useful to know. It does not state whether provider credentials must already be configured or how long the test takes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action, then cost/scope caveats, then the usage trigger. Every clause carries information an agent needs and nothing is repeated from the schema or annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters and an output schema present, the description only needs to cover what it does, what it touches, and when to call it — all three are present. The cost warning and the board-exclusion note close the remaining gaps an agent would otherwise have to guess at.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly refrains from inventing arguments.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb and target (test the configured text and vision models) and pins down the mechanism (three small synthetic JSON challenges) plus what it reports (semantic/schema failures). An agent can distinguish it from the board-oriented siblings at a glance.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a clear trigger condition: 'Use after changing model/provider settings.' Also adds an explicit exclusion, 'Does not read board contents,' which separates it from ingest_board and get_board_context. No alternative-tool routing is stated, but the exclusions do most of the work.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
diff_boardDiff Board SnapshotsARead-onlyIdempotent
Compare retained local snapshots of the same board, reporting cluster, node and connector changes. Names each changed node with its section and its old and new text, and each changed table cell with its row and column. Needs two ingests; when the board did not change in between, it reports no changes since the first. compareTo=1 selects the previous snapshot, 2 selects two states back. No network or LLM calls; ingest_board must capture the current Figma state first.
| Name | Required | Description | Default |
|---|---|---|---|
| boardId | Yes | The Figma file key, as returned by ingest_board, or the board URL | |
| compareTo | No | How many snapshots back to use as the baseline (1 = the ingest before the latest) |
Output Schema
| Name | Required | Description |
|---|---|---|
| stats | Yes | |
| boardId | Yes | |
| newClusters | Yes | |
| nodeChanges | No | Edited, added, then removed nodes in reading order; read whole texts with get_board_context and nodeIds |
| summaryText | Yes | Paste-ready human/LLM-readable change report |
| removedClusters | Yes | |
| addedConnections | Yes | |
| currentCreatedAt | Yes | ISO timestamp of the latest ingest |
| ignoredArguments | No | Unknown input keys that were ignored; their values are not echoed. Absent when none |
| modifiedClusters | Yes | |
| tableCellChanges | No | |
| baselineCreatedAt | Yes | ISO timestamp of the baseline ingest |
| currentSnapshotId | No | |
| baselineSnapshotId | No | |
| newClustersOmitted | No | New clusters beyond the first 20 |
| nodeChangesOmitted | No | Changed nodes beyond the first 100 |
| removedConnections | Yes | |
| removedClustersOmitted | No | Removed clusters beyond the first 20 |
| addedConnectionsOmitted | No | Added connections beyond the first 50 |
| modifiedClustersOmitted | No | Modified clusters beyond the first 20 |
| tableCellChangesOmitted | No | Table cell changes beyond the first 50 |
| removedConnectionsOmitted | No | Removed connections beyond the first 50 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, and the description reinforces this with 'No network or LLM calls' while adding genuinely new facts: the two-ingest requirement and the no-change result ('reports no changes since the first'). It also sketches what changed content gets reported, though it says nothing about retention limits or result size for large boards.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is front-loaded with the core purpose and wastes little space, packing prerequisites and parameter behavior into a few sentences. The node/table-cell reporting sentence partially duplicates the existing output schema and could be trimmed.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present and full annotation coverage, the description only needs to carry preconditions and scope, which it does. The remaining gap is minor: no indication of how many snapshots are retained or what happens if fewer than compareTo snapshots exist.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both parameters are already documented, including compareTo's baseline meaning. The description only restates it with an example ('compareTo=1 selects the previous snapshot, 2 selects two states back') and adds nothing about boardId beyond what the schema says.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The first sentence states a specific verb and resource ('Compare retained local snapshots of the same board') plus the outputs covered (cluster, node, connector changes). This clearly separates it from siblings like ingest_board, which capture state rather than compare it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a clear precondition ('Needs two ingests') and an ordering constraint ('ingest_board must capture the current Figma state first'), so an agent knows exactly when the tool is callable. It stops short of naming an explicit alternative or a when-not-to-use case, but no sibling competes for the same diff job.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_board_contextGet Board ContextARead-onlyIdempotent
Read source-cited context from an ingested board snapshot. Start overviews, summaries and documentation with a call without topic, nodeIds, limit and maxChars: its first page names the largest sections and lists sections with IDs. Then pass section, page, frame or group IDs as nodeIds; several IDs share each page in request order. For a whole-board summary, pass all top-level section IDs (at most 50 per call) with maxChars 24000, follow nextCursor, then read outsideSections: true. Default detail: "auto" switches reads of multiple distinct IDs or one page, section, frame or group to a compact overview only when the first full page would leave unread excerpts. Overview lines contain node IDs and deterministically shortened text (50–120 characters); structuredContent puts the excerpts once in overview.text, with empty evidence and clusters. limit applies only to the full view and is ignored in an overview, even when explicit. Read the complete source and Figma link with the same boardId and snapshotId, nodeIds: [""] and detail: "full"; table IDs read every row. Without overview, excerpts are in evidence. Read outsideSections: true, search with topic, or continue with cursor. Cite the node ID or Figma link behind each statement. Synthesize the answer yourself. No network or LLM calls; use ingest_board to refresh Figma content.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum evidence excerpts per full page (default 20, at most 100); ignored in an automatic overview, even when explicit. Use detail: full for an excerpt limit | |
| topic | No | Words to search for. An excerpt matches when at least one of them is in its text, its section or node name, the label of an arrow attached to it or, for a table row, its column headings, as a whole word ignoring case and accents (words of five or more letters also match compounds that begin with them); excerpts with more of the words come first. Other word forms, synonyms and translations do not match: include them yourself, for example "payment payments pay Bezahlung". Cannot be combined with nodeIds or outsideSections. | |
| cursor | No | nextCursor of the previous page, unchanged; send it with the same topic, nodeIds, outsideSections, detail, limit and maxChars | |
| detail | No | auto uses a compact, source-marked overview when a requested container or several nodeIds need multiple full pages; full returns linked evidence objects. Overview lines may be shortened; use full to read all text | auto |
| boardId | Yes | The Figma file key returned by ingest_board, or the board URL. A URL with a node-id, without nodeIds, topic and outsideSections, reads that node | |
| nodeIds | No | Read exact source nodes, all rows of a table or the row of a table cell, or every excerpt inside a page, section, frame or group by its ID (nested sections included, in reading order); several IDs in one call share every page in request order; cannot be combined with topic | |
| maxChars | No | Character budget for each representation: the readable text content and the JSON of structuredContent (default 12000, minimum 2000) | |
| snapshotId | No | Read a specific retained snapshot instead of the latest board | |
| outsideSections | No | Read every excerpt that lies in no section, cluster by cluster in reading order, tables row by row; on a board without sections, all excerpts. Cannot be combined with topic or nodeIds |
Output Schema
| Name | Required | Description |
|---|---|---|
| clusters | Yes | |
| evidence | Yes | Full linked excerpts; empty in overview mode, where excerpts are in overview.text instead |
| overview | No | Present only for automatic compact overview pages; evidence and clusters are empty, not a claim of no matches. Read a line's full text and Figma link with the same boardId and snapshotId, its nodeId, and detail: full |
| relations | No | Cluster-to-cluster relations derived from connector arrows |
| truncated | Yes | |
| nextCursor | No | |
| snapshotId | Yes | |
| truncation | Yes | Explicit omissions from structured results and the readable text |
| connections | Yes | Arrows with at least one end, or a section, frame or group around one, among this page's excerpts; never arrows to a page. The label is the text on the arrow |
| contextText | Yes | Orientation and reading instructions. Excerpts are in overview.text when overview is present (evidence and clusters are then empty), otherwise in evidence; text content carries the same readable excerpts |
| totalMatched | Yes | |
| unknownNodeIds | No | Requested nodeIds that are not in this snapshot; the others are read |
| ignoredArguments | No | Unknown input keys that were ignored; their values are not echoed. Absent when none |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive/closed-world behavior, and the description adds substantial context beyond them: no network or LLM calls, overview shortening to 50–120 characters, excerpts placed in structuredContent overview.text with empty evidence and clusters, limit being ignored in overview, and table IDs reading every row.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The content is valuable but delivered as a dense run-on paragraph with repeated overview explanations and nested clauses, making it hard to scan. The purpose is front-loaded, but the middle-to-end could be restructured into bullets for faster parsing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex 9-parameter read tool with full schema coverage, annotations, and an output schema, the description covers the key workflows: overview, full read, topic search, cursor pagination, outsideSections, and citations. Return values and safety are handled by structured fields, so nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds cross-parameter workflow semantics: omitting topic/nodeIds/limit/maxChars yields an overview, multiple nodeIds share pages in request order, whole-board summaries use top-level section IDs with maxChars 24000, and cursor must be reused with the same parameters. Much individual parameter documentation is already in the schema, so it is not a full 5.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The opening sentence names a specific verb and resource ('Read source-cited context from an ingested board snapshot') and distinguishes the tool from ingest_board by directing refresh calls there. The closing 'Synthesize the answer yourself' also implicitly separates it from answer_from_board, even though that sibling is not named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It prescribes a detailed sequence: start without topic/nodeIds/limit/maxChars to get an overview, then pass container IDs, use all top-level section IDs with maxChars 24000 for a whole-board summary, follow nextCursor, then read outsideSections. It also covers topic search and cursor continuation. It stops short of explicitly stating when to choose answer_from_board instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
ingest_boardIngest FigJam BoardA
Read a FigJam/Figma URL with the configured Figma token and persist a local snapshot for get_board_context, answer_from_board and diff_board; the summary names the largest sections to read next and how many excerpts lie outside sections. Leaves the Figma file unchanged. Every call downloads the board from Figma (one Tier 1 request); get_board_context and answer_from_board read the saved snapshot without a new request. Balanced/quality modes may send board text and images to the configured LLM provider and incur charges; max_speed skips vision. Re-ingest to refresh stale content and continue pending image interpretation; focusNodeIds with section IDs from the summary or the first page of get_board_context interprets their images first. Local history is bounded. Supports framework phases or customPhases.
| Name | Required | Description | Default |
|---|---|---|---|
| ingestMode | No | How aggressively to use vision LLM calls during ingest | balanced |
| customPhases | No | Free-form phase names to map clusters onto (e.g. ["Ideen", "Feedback", "Offene Fragen"]); overrides docStructureHint | |
| figmaFileUrl | Yes | URL of the FigJam/Figma file to ingest | |
| focusNodeIds | No | IDs of pages, sections, frames, groups or single nodes whose image clusters are interpreted first, in list order; the rest of the board follows in the usual order. Section IDs come from the ingest_board summary or the first page of get_board_context. Only the order of image interpretation changes: the whole board is still read and cached, and later ingests without focusNodeIds reuse the interpretations. No effect in max_speed | |
| forceFullIngest | No | Build the snapshot from the downloaded board again instead of the cached result for unchanged content, e.g. after turning credential redaction off. Image interpretations of unchanged clusters are kept, as without forceFullIngest; clusters still pending are interpreted as on any ingest. Model and prompt changes are detected automatically, so forceFullIngest is not needed for them. An unchanged board gives no new snapshot for diff_board. Default: false | |
| docStructureHint | No | Built-in framework used to map clusters to phases | freeform |
| figmaAccessToken | No | Figma personal access token; falls back to FIGMA_ACCESS_TOKEN env var if omitted |
Output Schema
| Name | Required | Description |
|---|---|---|
| boardId | Yes | |
| summary | Yes | |
| ingestMode | No | |
| snapshotId | No | |
| clusterCount | Yes | |
| figmaVersion | No | |
| qualityReport | No | |
| relationCount | No | Directed cluster-to-cluster relations derived from connector arrows |
| ignoredArguments | No | Unknown input keys that were ignored; their values are not echoed. Absent when none |
| freshnessCheckedAt | No | |
| persistenceWarning | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds substantial behavior beyond the annotations: the Figma file is left unchanged, every call costs exactly one Tier 1 Figma request, balanced/quality modes may incur LLM charges while max_speed skips vision, and local history is bounded. These are exactly the cost, side-effect and safety facts an agent needs before invoking an open-world, non-idempotent tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose is front-loaded in the first clause, but the body is a single dense run-on block mixing cost, caching, vision ordering and phase mapping. It also restates focusNodeIds semantics already fully documented in the schema, so several clauses do not earn their place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 7-parameter ingest tool with an output schema, the description covers cost model, caching/idempotency behavior, staleness, refresh path and downstream consumers. Nothing an agent needs to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining the cost/vision tradeoff behind ingestMode and the resolution path for focusNodeIds section IDs. It adds little on figmaAccessToken and docStructureHint beyond what the schema already says.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a concrete verb+resource (read a FigJam/Figma URL, persist a local snapshot) and immediately ties the result to the three sibling tools that consume it. An agent can distinguish this ingest step from get_board_context/answer_from_board/diff_board without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit refresh guidance ("Re-ingest to refresh stale content and continue pending image interpretation") and clarifies that siblings read the saved snapshot with no new request, which implicitly tells the agent when not to call this tool. It stops short of an explicit "use X instead when the snapshot is fresh" routing rule, so 4 rather than 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
v0.12.0- Changed
answer_from_board5 fields changed- changed
Input schema / properties / boardId / descriptionPrevious value: -"The Figma file key returned by ingest_board"New value: +"The Figma file key returned by ingest_board, or the board URL" - changed
Input schema / properties / boardId / maxLengthPrevious value: -128New value: +2048 - removed
Input schema / properties / boardId / patternRemoved value: -"^[A-Za-z0-9]+$" - added
Output schema / properties / citations / items / properties / frameNamesAdded value: +{ + "description": "Names of enclosing frames and groups, outermost first", + "items": { + "maxLength": 80, + "type": "string" + }, + "maxItems": 16, + "type": "array" +} - added
Output schema / properties / ignoredArgumentsAdded value: +{ + "description": "Unknown input keys that were ignored; their values are not echoed. Absent when none", + "items": { + "type": "string" + }, + "type": "array" +}
- Changed
diagnose_llm_config1 field changed- added
Output schema / properties / ignoredArgumentsAdded value: +{ + "description": "Unknown input keys that were ignored; their values are not echoed. Absent when none", + "items": { + "type": "string" + }, + "type": "array" +}
- Changed
diff_board14 fields changed- changed
Input schema / properties / boardId / descriptionPrevious value: -"The Figma file key, as returned by ingest_board"New value: +"The Figma file key, as returned by ingest_board, or the board URL" - changed
Input schema / properties / boardId / maxLengthPrevious value: -128New value: +2048 - removed
Input schema / properties / boardId / patternRemoved value: -"^[A-Za-z0-9]+$" - added
Output schema / properties / addedConnectionsOmittedAdded value: +{ + "description": "Added connections beyond the first 50", + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" +} - added
Output schema / properties / ignoredArgumentsAdded value: +{ + "description": "Unknown input keys that were ignored; their values are not echoed. Absent when none", + "items": { + "type": "string" + }, + "type": "array" +} - added
Output schema / properties / modifiedClustersOmittedAdded value: +{ + "description": "Modified clusters beyond the first 20", + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" +} - added
Output schema / properties / newClustersOmittedAdded value: +{ + "description": "New clusters beyond the first 20", + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" +} - added
Output schema / properties / removedClustersOmittedAdded value: +{ + "description": "Removed clusters beyond the first 20", + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" +} - added
Output schema / properties / removedConnectionsOmittedAdded value: +{ + "description": "Removed connections beyond the first 50", + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" +} - added
Output schema / properties / tableCellChanges / items / properties / currentColumn / descriptionAdded value: +"0-based, as in get_board_context" - added
Output schema / properties / tableCellChanges / items / properties / currentRow / descriptionAdded value: +"0-based, as in get_board_context" - added
Output schema / properties / tableCellChanges / items / properties / previousColumn / descriptionAdded value: +"0-based, as in get_board_context" - added
Output schema / properties / tableCellChanges / items / properties / previousRow / descriptionAdded value: +"0-based, as in get_board_context" - added
Output schema / properties / tableCellChangesOmittedAdded value: +{ + "description": "Table cell changes beyond the first 50", + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" +}
- Changed
get_board_context7 fields changed- changed
Input schema / properties / boardId / descriptionPrevious value: -"The Figma file key returned by ingest_board"New value: +"The Figma file key returned by ingest_board, or the board URL. A URL with a node-id, without nodeIds, topic and outsideSections, reads that node" - changed
Input schema / properties / boardId / maxLengthPrevious value: -128New value: +2048 - removed
Input schema / properties / boardId / patternRemoved value: -"^[A-Za-z0-9]+$" - changed
Input schema / properties / topic / descriptionPrevious value: -"Optional topic to focus the context on"New value: +"Words to search for. An excerpt matches when at least one of them is in its text, its section or node name, the label of an arrow attached to it or, for a table row, its column headings, as a whole word ignoring case and accents (words of five or more letters also match compounds that begin with them); excerpts with more of the words come first. Other word forms, synonyms and translations do not match: include them yourself, for example \"payment payments pay Bezahlung\". Cannot be combined with nodeIds or outsideSections." - added
Output schema / properties / clusters / items / properties / frameNamesAdded value: +{ + "description": "Named enclosing frames and groups, outermost first; excerpts repeat them only where they differ", + "items": { + "maxLength": 80, + "type": "string" + }, + "maxItems": 16, + "type": "array" +} - added
Output schema / properties / evidence / items / properties / frameNamesAdded value: +{ + "description": "Named enclosing frames and groups, outermost first; included only when nonempty and different from the cluster", + "items": { + "maxLength": 80, + "type": "string" + }, + "maxItems": 16, + "type": "array" +} - added
Output schema / properties / ignoredArgumentsAdded value: +{ + "description": "Unknown input keys that were ignored; their values are not echoed. Absent when none", + "items": { + "type": "string" + }, + "type": "array" +}
- Changed
ingest_board1 field changed- added
Output schema / properties / ignoredArgumentsAdded value: +{ + "description": "Unknown input keys that were ignored; their values are not echoed. Absent when none", + "items": { + "type": "string" + }, + "type": "array" +}
2 tool updates
v0.10.3- Changed
diff_board3 fields changed- added
Output schema / properties / modifiedClusters / items / properties / sectionAdded value: +{ + "description": "Name of the innermost section around the cluster; absent outside sections", + "type": "string" +} - added
Output schema / properties / newClusters / items / properties / sectionAdded value: +{ + "description": "Name of the innermost section around the cluster; absent outside sections", + "type": "string" +} - added
Output schema / properties / removedClusters / items / properties / sectionAdded value: +{ + "description": "Name of the innermost section around the cluster; absent outside sections", + "type": "string" +}
- Changed
get_board_context16 fields changed- changed
Input schema / properties / cursor / descriptionPrevious value: -"nextCursor of the previous page, unchanged; send it with the same topic, nodeIds, outsideSections, limit and maxChars"New value: +"nextCursor of the previous page, unchanged; send it with the same topic, nodeIds, outsideSections, detail, limit and maxChars" - added
Input schema / properties / detailAdded value: +{ + "default": "auto", + "description": "auto uses a compact, source-marked overview when a requested container or several nodeIds need multiple full pages; full returns linked evidence objects. Overview lines may be shortened; use full to read all text", + "enum": [ + "auto", + "full" + ], + "type": "string" +} - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum evidence excerpts per page (default 20)"New value: +"Maximum evidence excerpts per full page (default 20, at most 100); ignored in an automatic overview, even when explicit. Use detail: full for an excerpt limit" - changed
Input schema / properties / maxChars / descriptionPrevious value: -"Character budget for each representation: the readable text content and the JSON of structuredContent (default 12000)"New value: +"Character budget for each representation: the readable text content and the JSON of structuredContent (default 12000, minimum 2000)" - changed
Input schema / properties / maxChars / minimumPrevious value: -512New value: +2000 - changed
Output schema / properties / clusters / items / properties / summary / descriptionPrevious value: -"Model summary of the cluster; empty for deterministic clusters, whose excerpts carry the text"New value: +"Model summary of the cluster; empty for deterministic clusters, whose excerpts carry the text, and where maxChars leaves no room for it" - changed
Output schema / properties / contextText / descriptionPrevious value: -"Orientation: board header, page position, board overview or subsections. The excerpts are in evidence; the text content carries the readable version"New value: +"Orientation and reading instructions. Excerpts are in overview.text when overview is present (evidence and clusters are then empty), otherwise in evidence; text content carries the same readable excerpts" - added
Output schema / properties / evidence / descriptionAdded value: +"Full linked excerpts; empty in overview mode, where excerpts are in overview.text instead" - added
Output schema / properties / evidence / items / properties / chunkIndex / descriptionAdded value: +"Absent means 0" - added
Output schema / properties / evidence / items / properties / modelDerived / descriptionAdded value: +"Absent means false, independent of the cluster's modelDerived" - added
Output schema / properties / evidence / items / properties / snapshotId / descriptionAdded value: +"Omitted when inherited from the response snapshotId; only snapshotId is inherited" - added
Output schema / properties / evidence / items / properties / truncated / descriptionAdded value: +"Absent means false, independent of the cluster" - changed
Output schema / properties / evidence / items / requiredPrevious value: -[ - "evidenceId", - "snapshotId", - "nodeId", - "text", - "sourceType", - "modelDerived", - "chunkIndex", - "url", - "truncated" -]New value: +[ + "evidenceId", + "nodeId", + "text", + "sourceType", + "url" +] - added
Output schema / properties / overviewAdded value: +{ + "additionalProperties": false, + "description": "Present only for automatic compact overview pages; evidence and clusters are empty, not a claim of no matches. Read a line's full text and Figma link with the same boardId and snapshotId, its nodeId, and detail: full", + "properties": { + "shortenedEvidence": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "shownEvidence": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "text": { + "description": "Source-marked excerpt lines grouped by innermost section; the excerpt texts occur only here in structuredContent", + "type": "string" + }, + "textLimit": { + "maximum": 120, + "minimum": 50, + "type": "integer" + } + }, + "required": [ + "text", + "shownEvidence", + "shortenedEvidence", + "textLimit" + ], + "type": "object" +} - added
Output schema / properties / truncation / properties / omittedSummariesAdded value: +{ + "description": "Clusters on this page whose model summary is left empty to fit maxChars", + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" +} - added
Output schema / properties / unknownNodeIdsAdded value: +{ + "description": "Requested nodeIds that are not in this snapshot; the others are read", + "items": { + "type": "string" + }, + "type": "array" +}
4 tool updates
v0.10.2- Changed
diagnose_llm_config1 field changed- added
Output schema / properties / checks / items / properties / attemptsAdded value: +{ + "description": "The model candidates tried, in order; error is the provider's message or the error", + "items": { + "additionalProperties": false, + "properties": { + "error": { + "type": "string" + }, + "model": { + "type": "string" + }, + "ok": { + "type": "boolean" + } + }, + "required": [ + "model", + "ok" + ], + "type": "object" + }, + "type": "array" +}
- Changed
diff_board5 fields changed- added
Output schema / properties / nodeChangesAdded value: +{ + "description": "Edited, added, then removed nodes in reading order; read whole texts with get_board_context and nodeIds", + "items": { + "additionalProperties": false, + "properties": { + "changeType": { + "enum": [ + "added", + "removed", + "edited" + ], + "type": "string" + }, + "changes": { + "items": { + "enum": [ + "text", + "name", + "image", + "rotation", + "type", + "appearance" + ], + "type": "string" + }, + "type": "array" + }, + "currentText": { + "description": "Whitespace-collapsed; only the changed part of a long text", + "type": "string" + }, + "name": { + "type": "string" + }, + "nodeId": { + "type": "string" + }, + "nodeType": { + "type": "string" + }, + "previousName": { + "type": "string" + }, + "previousText": { + "description": "Whitespace-collapsed; only the changed part of a long text", + "type": "string" + }, + "section": { + "type": "string" + }, + "sectionId": { + "description": "Innermost section; absent outside sections", + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "nodeId", + "changeType", + "nodeType", + "url" + ], + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / nodeChangesOmittedAdded value: +{ + "description": "Changed nodes beyond the first 100", + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" +} - added
Output schema / properties / tableCellChanges / items / properties / columnLabelAdded value: +{ + "description": "Text of the cell in the first row of the column", + "type": "string" +} - added
Output schema / properties / tableCellChanges / items / properties / rowLabelAdded value: +{ + "description": "Text of the first cell in the row", + "type": "string" +} - added
Output schema / properties / tableCellChanges / items / properties / tableNameAdded value: +{ + "type": "string" +}
- Changed
get_board_context4 fields changed- changed
Input schema / properties / cursor / descriptionPrevious value: -"Continue a page using the same query, snapshot, limit and maxChars"New value: +"nextCursor of the previous page, unchanged; send it with the same topic, nodeIds, outsideSections, limit and maxChars" - added
Output schema / properties / connections / descriptionAdded value: +"Arrows with at least one end, or a section, frame or group around one, among this page's excerpts; never arrows to a page. The label is the text on the arrow" - added
Output schema / properties / connections / items / properties / fromTextAdded value: +{ + "description": "Short text or name of the start node when it is not among this page's excerpts, redacted like excerpts", + "maxLength": 80, + "type": "string" +} - added
Output schema / properties / connections / items / properties / toTextAdded value: +{ + "description": "Short text or name of the end node when it is not among this page's excerpts, redacted like excerpts", + "maxLength": 80, + "type": "string" +}
- Changed
ingest_board3 fields changed- added
Input schema / properties / focusNodeIdsAdded value: +{ + "description": "IDs of pages, sections, frames, groups or single nodes whose image clusters are interpreted first, in list order; the rest of the board follows in the usual order. Section IDs come from the ingest_board summary or the first page of get_board_context. Only the order of image interpretation changes: the whole board is still read and cached, and later ingests without focusNodeIds reuse the interpretations. No effect in max_speed", + "items": { + "maxLength": 200, + "minLength": 1, + "type": "string" + }, + "maxItems": 50, + "minItems": 1, + "type": "array" +} - changed
Input schema / properties / forceFullIngest / descriptionPrevious value: -"Download and extract the board again, skipping the unchanged-board check and cache, and redo the image interpretation of the chosen ingestMode. Interpretations this mode does not redo (all in max_speed; in balanced those of clusters without image or drawing) are kept while a cluster's content is unchanged. The vision time budget still applies, so balanced and max_quality may need several ingests until every image is interpreted again. An unchanged board gives no new snapshot for diff_board, even with forceFullIngest. Model/configuration changes are detected automatically. Default: false"New value: +"Build the snapshot from the downloaded board again instead of the cached result for unchanged content, e.g. after turning credential redaction off. Image interpretations of unchanged clusters are kept, as without forceFullIngest; clusters still pending are interpreted as on any ingest. Model and prompt changes are detected automatically, so forceFullIngest is not needed for them. An unchanged board gives no new snapshot for diff_board. Default: false" - added
Output schema / properties / qualityReport / properties / focusAdded value: +{ + "additionalProperties": false, + "description": "Only with focusNodeIds: the IDs found on the board and the clusters in focus this ingestMode interprets, of them interpreted and pending", + "properties": { + "foundIds": { + "items": { + "type": "string" + }, + "type": "array" + }, + "imageClusters": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "interpreted": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "pending": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "requestedIds": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "requestedIds", + "foundIds", + "imageClusters", + "interpreted", + "pending" + ], + "type": "object" +}
2 tool updates
v0.8.0- Changed
get_board_context2 fields changed- changed
Input schema / properties / nodeIds / descriptionPrevious value: -"Read exact source nodes, all rows of a table or the row of a table cell, or every excerpt inside a page, section, frame or group by its ID (nested sections included, in reading order); cannot be combined with topic"New value: +"Read exact source nodes, all rows of a table or the row of a table cell, or every excerpt inside a page, section, frame or group by its ID (nested sections included, in reading order); several IDs in one call share every page in request order; cannot be combined with topic" - added
Input schema / properties / outsideSectionsAdded value: +{ + "description": "Read every excerpt that lies in no section, cluster by cluster in reading order, tables row by row; on a board without sections, all excerpts. Cannot be combined with topic or nodeIds", + "type": "boolean" +}
- Changed
ingest_board2 fields changed- changed
Input schema / properties / forceFullIngest / descriptionPrevious value: -"Deliberately skip all caching and incremental reuse, including successful interpretations. The vision time budget still applies. Model/configuration changes are detected automatically. Default: false"New value: +"Download and extract the board again, skipping the unchanged-board check and cache, and redo the image interpretation of the chosen ingestMode. Interpretations this mode does not redo (all in max_speed; in balanced those of clusters without image or drawing) are kept while a cluster's content is unchanged. The vision time budget still applies, so balanced and max_quality may need several ingests until every image is interpreted again. An unchanged board gives no new snapshot for diff_board, even with forceFullIngest. Model/configuration changes are detected automatically. Default: false" - added
Output schema / properties / qualityReport / properties / figmaRequestsAdded value: +{ + "additionalProperties": false, + "description": "Figma requests of this ingest for images: image fills (Tier 2) and renders (Tier 1)", + "properties": { + "imageFills": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "renders": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "imageFills", + "renders" + ], + "type": "object" +}
2 tool updates
v0.7.0- Changed
answer_from_board1 field changed- changed
Output schema / properties / citations / items / properties / sourceType / enumPrevious value: -[ - "board_text", - "table_cell", - "board_metadata", - "model_interpretation", - "cluster_summary" -]New value: +[ + "board_text", + "table_cell", + "table_row", + "board_metadata", + "model_interpretation", + "cluster_summary" +]
- Changed
get_board_context9 fields changed- changed
Input schema / properties / maxChars / descriptionPrevious value: -"Character budget for the whole structured result (JSON of structuredContent, including contextText; default 12000)"New value: +"Character budget for each representation: the readable text content and the JSON of structuredContent (default 12000)" - changed
Input schema / properties / nodeIds / descriptionPrevious value: -"Read exact source nodes or table cells; cannot be combined with topic"New value: +"Read exact source nodes, all rows of a table or the row of a table cell, or every excerpt inside a page, section, frame or group by its ID (nested sections included, in reading order); cannot be combined with topic" - added
Output schema / properties / clusters / items / properties / pageNameAdded value: +{ + "description": "Page of this cluster's excerpts on this page of results; excerpts repeat it only where they differ", + "maxLength": 160, + "type": "string" +} - added
Output schema / properties / clusters / items / properties / sectionNamesAdded value: +{ + "description": "Enclosing sections, outermost first, of this cluster's excerpts; excerpts repeat them only where they differ", + "items": { + "maxLength": 80, + "type": "string" + }, + "maxItems": 16, + "type": "array" +} - added
Output schema / properties / clusters / items / properties / summary / descriptionAdded value: +"Model summary of the cluster; empty for deterministic clusters, whose excerpts carry the text" - added
Output schema / properties / contextText / descriptionAdded value: +"Orientation: board header, page position, board overview or subsections. The excerpts are in evidence; the text content carries the readable version" - added
Output schema / properties / evidence / items / properties / pageName / descriptionAdded value: +"Only for an excerpt outside the listed clusters or whose location differs from its cluster's" - added
Output schema / properties / evidence / items / properties / sectionNames / descriptionAdded value: +"Same rule as pageName; an empty list means outside sections" - changed
Output schema / properties / evidence / items / properties / sourceType / enumPrevious value: -[ - "board_text", - "table_cell", - "board_metadata", - "model_interpretation", - "cluster_summary" -]New value: +[ + "board_text", + "table_cell", + "table_row", + "board_metadata", + "model_interpretation", + "cluster_summary" +]
1 tool update
v0.6.0- Changed
get_board_context1 field changed- changed
Input schema / properties / maxChars / descriptionPrevious value: -"Character budget for the readable context (default 12000)"New value: +"Character budget for the whole structured result (JSON of structuredContent, including contextText; default 12000)"
5 tool updates
v0.4.0- Changed
answer_from_board13 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / additionalPropertiesRemoved value: -false - added
Input schema / properties / boardId / descriptionAdded value: +"The Figma file key returned by ingest_board" - added
Input schema / properties / boardId / maxLengthAdded value: +128 - added
Input schema / properties / boardId / minLengthAdded value: +6 - added
Input schema / properties / boardId / patternAdded value: +"^[A-Za-z0-9]+$" - added
Input schema / properties / question / maxLengthAdded value: +2000 - added
Input schema / properties / question / minLengthAdded value: +1 - added
Input schema / properties / snapshotIdAdded value: +{ + "maxLength": 128, + "minLength": 1, + "pattern": "^[A-Za-z0-9_-]+$", + "type": "string" +} - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / properties / citationsAdded value: +{ + "items": { + "additionalProperties": false, + "properties": { + "clusterId": { + "type": "string" + }, + "clusterLabel": { + "type": "string" + }, + "column": { + "type": "number" + }, + "evidenceId": { + "type": "string" + }, + "modelDerived": { + "type": "boolean" + }, + "nodeId": { + "type": "string" + }, + "nodeName": { + "maxLength": 160, + "type": "string" + }, + "pageId": { + "type": "string" + }, + "pageName": { + "maxLength": 160, + "type": "string" + }, + "quote": { + "type": "string" + }, + "row": { + "type": "number" + }, + "sectionIds": { + "items": { + "type": "string" + }, + "type": "array" + }, + "sectionNames": { + "items": { + "maxLength": 80, + "type": "string" + }, + "maxItems": 16, + "type": "array" + }, + "snapshotId": { + "type": "string" + }, + "sourceType": { + "enum": [ + "board_text", + "table_cell", + "board_metadata", + "model_interpretation", + "cluster_summary" + ], + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "evidenceId", + "snapshotId", + "nodeId", + "quote", + "url", + "sourceType", + "modelDerived" + ], + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / snapshotIdAdded value: +{ + "type": "string" +} - changed
Output schema / requiredPrevious value: -[ - "answer", - "citedClusters" -]New value: +[ + "answer", + "citedClusters", + "snapshotId", + "citations" +]
- Added
diagnose_llm_config - Added
diff_board - Changed
get_board_context27 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / additionalPropertiesRemoved value: -false - added
Input schema / properties / boardId / descriptionAdded value: +"The Figma file key returned by ingest_board" - added
Input schema / properties / boardId / maxLengthAdded value: +128 - added
Input schema / properties / boardId / minLengthAdded value: +6 - added
Input schema / properties / boardId / patternAdded value: +"^[A-Za-z0-9]+$" - added
Input schema / properties / cursorAdded value: +{ + "description": "Continue a page using the same query, snapshot, limit and maxChars", + "maxLength": 2048, + "minLength": 1, + "type": "string" +} - added
Input schema / properties / limitAdded value: +{ + "default": 20, + "description": "Maximum evidence excerpts per page (default 20)", + "maximum": 100, + "minimum": 1, + "type": "integer" +} - added
Input schema / properties / maxCharsAdded value: +{ + "default": 12000, + "description": "Character budget for the readable context (default 12000)", + "maximum": 24000, + "minimum": 512, + "type": "integer" +} - added
Input schema / properties / nodeIdsAdded value: +{ + "description": "Read exact source nodes or table cells; cannot be combined with topic", + "items": { + "maxLength": 200, + "minLength": 1, + "type": "string" + }, + "maxItems": 50, + "minItems": 1, + "type": "array" +} - added
Input schema / properties / snapshotIdAdded value: +{ + "description": "Read a specific retained snapshot instead of the latest board", + "maxLength": 128, + "minLength": 1, + "pattern": "^[A-Za-z0-9_-]+$", + "type": "string" +} - added
Input schema / properties / topic / maxLengthAdded value: +200 - added
Input schema / properties / topic / minLengthAdded value: +1 - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / properties / clusters / items / properties / modelDerivedAdded value: +{ + "description": "True for model summaries and summaries whose non-model origin cannot be established", + "type": "boolean" +} - added
Output schema / properties / clusters / items / properties / sourceNodeIds / descriptionAdded value: +"Source nodes displayed on this page, not citations validating the cluster summary" - added
Output schema / properties / clusters / items / properties / summarySourceAdded value: +{ + "description": "Origin of the derived cluster summary; the summary is not verbatim source evidence", + "enum": [ + "vision_llm", + "text_llm", + "deterministic", + "cache", + "unknown" + ], + "type": "string" +} - changed
Output schema / properties / clusters / items / requiredPrevious value: -[ - "label", - "summary", - "sourceNodeIds" -]New value: +[ + "label", + "summary", + "summarySource", + "modelDerived", + "sourceNodeIds" +] - added
Output schema / properties / connectionsAdded value: +{ + "items": { + "additionalProperties": false, + "properties": { + "connectorId": { + "type": "string" + }, + "direction": { + "enum": [ + "forward", + "reverse", + "bidirectional", + "undirected" + ], + "type": "string" + }, + "fromNodeId": { + "type": "string" + }, + "label": { + "type": "string" + }, + "toNodeId": { + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "connectorId", + "fromNodeId", + "toNodeId", + "direction", + "url" + ], + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / evidenceAdded value: +{ + "items": { + "additionalProperties": false, + "properties": { + "chunkIndex": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "clusterId": { + "type": "string" + }, + "clusterLabel": { + "type": "string" + }, + "column": { + "type": "number" + }, + "evidenceId": { + "type": "string" + }, + "modelDerived": { + "type": "boolean" + }, + "nodeId": { + "type": "string" + }, + "nodeName": { + "maxLength": 160, + "type": "string" + }, + "pageId": { + "type": "string" + }, + "pageName": { + "maxLength": 160, + "type": "string" + }, + "renderNodeId": { + "type": "string" + }, + "row": { + "type": "number" + }, + "sectionIds": { + "items": { + "type": "string" + }, + "type": "array" + }, + "sectionNames": { + "items": { + "maxLength": 80, + "type": "string" + }, + "maxItems": 16, + "type": "array" + }, + "snapshotId": { + "type": "string" + }, + "sourceType": { + "enum": [ + "board_text", + "table_cell", + "board_metadata", + "model_interpretation", + "cluster_summary" + ], + "type": "string" + }, + "text": { + "type": "string" + }, + "truncated": { + "type": "boolean" + }, + "url": { + "type": "string" + } + }, + "required": [ + "evidenceId", + "snapshotId", + "nodeId", + "text", + "sourceType", + "modelDerived", + "chunkIndex", + "url", + "truncated" + ], + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / nextCursorAdded value: +{ + "type": "string" +} - added
Output schema / properties / relationsAdded value: +{ + "description": "Cluster-to-cluster relations derived from connector arrows", + "items": { + "additionalProperties": false, + "properties": { + "edgeCount": { + "exclusiveMinimum": 0, + "maximum": 9007199254740991, + "type": "integer" + }, + "from": { + "description": "Label of the source cluster", + "type": "string" + }, + "label": { + "description": "Connector label(s), when the arrows are annotated", + "type": "string" + }, + "to": { + "description": "Label of the target cluster", + "type": "string" + } + }, + "required": [ + "from", + "to", + "edgeCount" + ], + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / snapshotIdAdded value: +{ + "type": "string" +} - added
Output schema / properties / totalMatchedAdded value: +{ + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" +} - added
Output schema / properties / truncatedAdded value: +{ + "type": "boolean" +} - added
Output schema / properties / truncationAdded value: +{ + "additionalProperties": false, + "description": "Explicit omissions from structured results and the readable text", + "properties": { + "omittedConnections": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "omittedRelations": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "omittedTextConnections": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "omittedTextRelations": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "remainingEvidence": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "remainingEvidence", + "omittedConnections", + "omittedRelations", + "omittedTextConnections", + "omittedTextRelations" + ], + "type": "object" +} - changed
Output schema / requiredPrevious value: -[ - "contextText", - "clusters" -]New value: +[ + "contextText", + "clusters", + "snapshotId", + "evidence", + "connections", + "totalMatched", + "truncated", + "truncation" +]
- Changed
ingest_board22 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / additionalPropertiesRemoved value: -false - added
Input schema / properties / customPhasesAdded value: +{ + "description": "Free-form phase names to map clusters onto (e.g. [\"Ideen\", \"Feedback\", \"Offene Fragen\"]); overrides docStructureHint", + "items": { + "maxLength": 80, + "minLength": 1, + "type": "string" + }, + "maxItems": 12, + "minItems": 1, + "type": "array" +} - changed
Input schema / properties / docStructureHint / descriptionPrevious value: -"How to interpret the board's structure when mapping clusters to phases"New value: +"Built-in framework used to map clusters to phases" - changed
Input schema / properties / docStructureHint / enumPrevious value: -[ - "double_diamond", - "freeform" -]New value: +[ + "freeform", + "double_diamond", + "lean_canvas", + "retro", + "user_journey" +] - added
Input schema / properties / figmaAccessToken / maxLengthAdded value: +512 - added
Input schema / properties / figmaAccessToken / minLengthAdded value: +1 - added
Input schema / properties / figmaFileUrl / maxLengthAdded value: +2048 - added
Input schema / properties / forceFullIngestAdded value: +{ + "description": "Deliberately skip all caching and incremental reuse, including successful interpretations. The vision time budget still applies. Model/configuration changes are detected automatically. Default: false", + "type": "boolean" +} - added
Input schema / properties / ingestModeAdded value: +{ + "default": "balanced", + "description": "How aggressively to use vision LLM calls during ingest", + "enum": [ + "balanced", + "max_quality", + "max_speed" + ], + "type": "string" +} - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / properties / boardId / maxLengthAdded value: +128 - added
Output schema / properties / boardId / minLengthAdded value: +6 - added
Output schema / properties / boardId / patternAdded value: +"^[A-Za-z0-9]+$" - added
Output schema / properties / clusterCount / maximumAdded value: +9007199254740991 - added
Output schema / properties / figmaVersionAdded value: +{ + "type": "string" +} - added
Output schema / properties / freshnessCheckedAtAdded value: +{ + "type": "string" +} - added
Output schema / properties / ingestModeAdded value: +{ + "enum": [ + "balanced", + "max_quality", + "max_speed" + ], + "type": "string" +} - added
Output schema / properties / persistenceWarningAdded value: +{ + "type": "string" +} - added
Output schema / properties / qualityReportAdded value: +{ + "additionalProperties": false, + "properties": { + "cachedClusters": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "deterministicClusters": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "fallbackCount": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "fallbackReasons": { + "additionalProperties": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "propertyNames": { + "type": "string" + }, + "type": "object" + }, + "incompleteClusters": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "modelsUsed": { + "items": { + "type": "string" + }, + "type": "array" + }, + "nextRetryAt": { + "type": "number" + }, + "reusedClusters": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "visionClusters": { + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "modelsUsed", + "cachedClusters", + "deterministicClusters", + "visionClusters", + "fallbackCount" + ], + "type": "object" +} - added
Output schema / properties / relationCountAdded value: +{ + "description": "Directed cluster-to-cluster relations derived from connector arrows", + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" +} - added
Output schema / properties / snapshotIdAdded value: +{ + "type": "string" +}
3 tool updates
v0.1.0- First observed
answer_from_board - First observed
get_board_context - First observed
ingest_board
TDQS
Scored across 5 tools
Each tool maps to a distinct role: ingest (fetch snapshot), read/summarize (get_board_context), specific Q&A (answer_from_board), compare snapshots (diff_board), and config self-test (diagnose_llm_config). The main risk area is get_board_context vs answer_from_board, which both read from the same snapshot; the descriptions spend a lot of text partitioning them (summaries vs single factual questions), which mostly resolves the overlap but shows the boundary is not self-evident.
All names are snake_case and verb-first (ingest_board, get_board_context, answer_from_board, diff_board, diagnose_llm_config). The verbs vary in form (plain verb, verb_prepositional, verb_object_object), but the pattern remains readable and predictable.
Five tools is well-scoped for a board-snapshot context server: one write path, two read paths, one comparison, one diagnostics. No tool appears redundant or bolted on.
The lifecycle is covered: ingest, summarized/structured reading with cursors and search, targeted Q&A, snapshot diffing, and model diagnostics. Minor gaps exist around snapshot management (no explicit list/delete/prune of the bounded local history or snapshot inventory), but compareTo and re-ingest let agents work around these.
Maintenance
Related MCP Connectors
Read, create and edit noddle diagram boards, browse versions and comment as an AI collaborator.
Read and write Mural workspaces, rooms, templates, murals and widgets from your AI assistant.
Access Pollinations models and API capabilities through agent tools.
Bounded tools for rendering, extraction, RAG, enrichment, local discovery and review analysis.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables MCP-compatible LLMs to interact with Miro whiteboards to manage boards, create and manipulate shapes, and organize content through grouping tools.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically interact with a Miro board through the Miro API, supporting operations like creating items, updating positions, and managing connectors.16ISC
- FlicenseBqualityDmaintenanceEnables AI agents to read, inspect, and export Figma designs programmatically. Provides tools for listing components, styles, and exporting assets in various formats.51-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to visualize tasks on a collaborative Sketchbord whiteboard by composing content into diagrams, editing them incrementally, and reading back the board including user-drawn additions.MIT