figjam-context-mcp

Answer From Board

answer_from_board

Read-only

Answers a specific question by finding relevant FigJam board excerpts and returning validated source citations or an insufficient-evidence result.

Instructions

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.

Input Schema

Name	Required	Description
`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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.12.0Nov 5, 2026

changedInput schema / properties / boardId / description

Previous value: -"The Figma file key returned by ingest_board"New value: +"The Figma file key returned by ingest_board, or the board URL"

changedInput schema / properties / boardId / maxLength
```
Previous value: -128New value: +2048
```
removedInput schema / properties / boardId / pattern
```
Removed value: -"^[A-Za-z0-9]+$"
```

addedOutput schema / properties / citations / items / properties / frameNames

Added value: +{
+  "description": "Names of enclosing frames and groups, outermost first",
+  "items": {
+    "maxLength": 80,
+    "type": "string"
+  },
+  "maxItems": 16,
+  "type": "array"
+}

addedOutput schema / properties / ignoredArguments

Added value: +{
+  "description": "Unknown input keys that were ignored; their values are not echoed. Absent when none",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedv0.7.0Oct 19, 2026

changedOutput schema / properties / citations / items / properties / sourceType / enum

Previous 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"
+]

Changed13 schema fields changedv0.4.0Oct 18, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / boardId / description

Added value: +"The Figma file key returned by ingest_board"

addedInput schema / properties / boardId / maxLength
```
Added value: +128
```
addedInput schema / properties / boardId / minLength
```
Added value: +6
```
addedInput schema / properties / boardId / pattern
```
Added value: +"^[A-Za-z0-9]+$"
```
addedInput schema / properties / question / maxLength
```
Added value: +2000
```
addedInput schema / properties / question / minLength
```
Added value: +1
```

addedInput schema / properties / snapshotId

Added value: +{
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9_-]+$",
+  "type": "string"
+}

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / citations

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

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

changedOutput schema / required

Previous value: -[
-  "answer",
-  "citedClusters"
-]New value: +[
+  "answer",
+  "citedClusters",
+  "snapshotId",
+  "citations"
+]

First observedv0.1.0Jul 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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.

Conciseness4/5

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.

Completeness4/5

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.

Parameters4/5

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.

Purpose5/5

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.

Usage Guidelines5/5

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.

Deploy Server