Skip to main content
Glama
figjam-context-mcp

figjam-context-mcp

Diff Board Snapshots

diff_board
Read-onlyIdempotent

Compare two ingested local snapshots of the same FigJam board to report cluster, node, and connector changes, naming changed nodes by section and table cells by row and column.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "boardId": "<boardId>"
    },
    "name": "diff_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYesThe Figma file key, as returned by ingest_board, or the board URL
compareToNoHow many snapshots back to use as the baseline (1 = the ingest before the latest)

Output Schema

NameRequiredDescriptionDefault
statsYes
boardIdYes
newClustersYes
nodeChangesNoEdited, added, then removed nodes in reading order; read whole texts with get_board_context and nodeIds
summaryTextYesPaste-ready human/LLM-readable change report
removedClustersYes
addedConnectionsYes
currentCreatedAtYesISO timestamp of the latest ingest
ignoredArgumentsNoUnknown input keys that were ignored; their values are not echoed. Absent when none
modifiedClustersYes
tableCellChangesNo
baselineCreatedAtYesISO timestamp of the baseline ingest
currentSnapshotIdNo
baselineSnapshotIdNo
newClustersOmittedNoNew clusters beyond the first 20
nodeChangesOmittedNoChanged nodes beyond the first 100
removedConnectionsYes
removedClustersOmittedNoRemoved clusters beyond the first 20
addedConnectionsOmittedNoAdded connections beyond the first 50
modifiedClustersOmittedNoModified clusters beyond the first 20
tableCellChangesOmittedNoTable cell changes beyond the first 50
removedConnectionsOmittedNoRemoved connections beyond the first 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv0.12.0
    • changedInput schema / properties / boardId / description
      Previous 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"
    • changedInput schema / properties / boardId / maxLength
      Previous value: -128New value: +2048
    • removedInput schema / properties / boardId / pattern
      Removed value: -"^[A-Za-z0-9]+$"
    • addedOutput schema / properties / addedConnectionsOmitted
      Added value: +{
      +  "description": "Added connections beyond the first 50",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • 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"
      +}
    • addedOutput schema / properties / modifiedClustersOmitted
      Added value: +{
      +  "description": "Modified clusters beyond the first 20",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / newClustersOmitted
      Added value: +{
      +  "description": "New clusters beyond the first 20",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / removedClustersOmitted
      Added value: +{
      +  "description": "Removed clusters beyond the first 20",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / removedConnectionsOmitted
      Added value: +{
      +  "description": "Removed connections beyond the first 50",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / tableCellChanges / items / properties / currentColumn / description
      Added value: +"0-based, as in get_board_context"
    • addedOutput schema / properties / tableCellChanges / items / properties / currentRow / description
      Added value: +"0-based, as in get_board_context"
    • addedOutput schema / properties / tableCellChanges / items / properties / previousColumn / description
      Added value: +"0-based, as in get_board_context"
    • addedOutput schema / properties / tableCellChanges / items / properties / previousRow / description
      Added value: +"0-based, as in get_board_context"
    • addedOutput schema / properties / tableCellChangesOmitted
      Added value: +{
      +  "description": "Table cell changes beyond the first 50",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. Changed3 schema fields changedv0.10.3
    • addedOutput schema / properties / modifiedClusters / items / properties / section
      Added value: +{
      +  "description": "Name of the innermost section around the cluster; absent outside sections",
      +  "type": "string"
      +}
    • addedOutput schema / properties / newClusters / items / properties / section
      Added value: +{
      +  "description": "Name of the innermost section around the cluster; absent outside sections",
      +  "type": "string"
      +}
    • addedOutput schema / properties / removedClusters / items / properties / section
      Added value: +{
      +  "description": "Name of the innermost section around the cluster; absent outside sections",
      +  "type": "string"
      +}
  3. Changed5 schema fields changedv0.10.2
    • addedOutput schema / properties / nodeChanges
      Added 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"
      +}
    • addedOutput schema / properties / nodeChangesOmitted
      Added value: +{
      +  "description": "Changed nodes beyond the first 100",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / tableCellChanges / items / properties / columnLabel
      Added value: +{
      +  "description": "Text of the cell in the first row of the column",
      +  "type": "string"
      +}
    • addedOutput schema / properties / tableCellChanges / items / properties / rowLabel
      Added value: +{
      +  "description": "Text of the first cell in the row",
      +  "type": "string"
      +}
    • addedOutput schema / properties / tableCellChanges / items / properties / tableName
      Added value: +{
      +  "type": "string"
      +}
  4. Addedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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.

Conciseness4/5

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.

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 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.

Parameters3/5

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

Schema description coverage is 100%, so both parameters are 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.

Purpose5/5

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.

Usage Guidelines4/5

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.