Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
compareA

Compare a design against a rendered implementation and return discrepancies (measured on kiyas's golden eval set: 90% mutation recall, zero false positives on identical pairs). Provide figma (frame URL) or designImage (local path or URL of a design screenshot), plus either target (a URL) or component (natural-language description; kiyas finds it in the codebase). No Figma token needed for designImage — if a Figma MCP server is connected, export the frame as an image with its screenshot tool and pass that here. Returns a reportId you can pass to get_diff_report or list_issues.

get_diff_reportA

Fetch a stored kiyas report by reportId. Defaults to JSON; pass format=html to fetch the rendered report. Returns the artifact path and (by default for JSON) inline content.

list_issuesA

List discrepancies from a stored kiyas report by reportId, optionally filtered by severity (all | high | medium | low).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

The three tools are clearly distinct: 'compare' creates a new comparison and returns a reportId, 'get_diff_report' retrieves a stored report, and 'list_issues' lists discrepancies from a report. No functional overlap exists.

Naming Consistency5/5

All tool names follow the verb_noun pattern: 'compare', 'get_diff_report', 'list_issues'. The pattern is consistent across the server.

Tool Count5/5

With 3 tools, the server is well-scoped for its purpose of comparing designs and implementations. Each tool serves a necessary step in the workflow without redundancy.

Completeness5/5

The tool set covers the complete lifecycle: creating a comparison, retrieving the full report, and listing filtered issues. No obvious gaps for the domain.

Maintenance

ActivitySlowing
ResponsivenessNo issues