Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_get_font_inventory

Counts fonts by family and style across text nodes in a Figma file, exposing mismatches for design-system consistency work.

Instructions

Which fonts the file actually uses, counted by text node (family / style). Consistency work needs this: a design system that claims one typeface and quietly uses three is the usual failure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "figma_get_font_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileKeyNoWhich connected Figma file to use: its fileKey (figma_whoami) or, when omitted, the only connected file. Required once more than one file is connected; figma_ping lists them.
allPagesNoCount every page, not just the current one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the counting semantics (per text node, not per style declaration), which is genuinely useful and hard to infer. It does not say whether the call is read-only, expensive on large files, or what the result structure looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, the payload is front-loaded, and the motivational clause is short. 'The usual failure' is rhetorical color rather than operational information, but it costs little.

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?

For a two-parameter read-only tool with no annotations and no output schema, the description covers scope (file-wide, all pages by default via schema) and result semantics (per-family/style counts). Only the exact return shape and cost on large files are unaddressed, which is minor here.

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 fileKey and allPages are already documented in the schema, including the multi-file requirement. The description adds nothing about either parameter, which is acceptable given the schema but is not net-new value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and measurement unit: fonts used by the file, counted by text node, keyed by family/style. The 'actually uses' framing also distinguishes it from tools that report declared styles, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Consistency work needs this' implies the design-system/typeface-audit scenario but gives no explicit when-not condition and names no alternative tool (e.g. variable defs or audit) for adjacent questions. Usage is inferable rather than specified.

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