Skip to main content
Glama

Originality Check

originality_check

Compare source and recreated design token JSON to score palette, typography, shape, and spacing similarity, with actionable tips to differentiate the new design.

Instructions

Compare two designs (the source and your recreation or reimagination) and score how similar their palette, typography, shape and spacing are, with tips to differentiate. Pass the JSON from extract_tokens or analyze_design for each. Deterministic, no API key needed.

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": {
      "source": "<source>",
      "candidate": "<candidate>"
    },
    "name": "originality_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesTokens or spec JSON of the original design
candidateYesTokens or spec JSON of the new design

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses that the tool is deterministic, requires no API key, that it is a read-only comparison, and that output includes per-dimension similarity plus actionable tips. It does not cover edge behavior such as malformed or partial token JSON, or the scale of the similarity score.

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

Conciseness5/5

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

Two sentences, no filler. The comparison and the dimensions scored are front-loaded, and the input-source and no-API-key facts follow as supporting detail.

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?

There is no output schema, so the description must indicate what comes back, and it does: similarity scores per design dimension plus differentiation tips. For a deterministic two-input comparison tool this is nearly sufficient; only the score scale and output shape are left implicit.

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 coverage is 100%, so both parameters are already documented as 'Tokens or spec JSON of the original/new design'. The description reinforces this by naming extract_tokens and analyze_design as the sources for that JSON, which is genuinely useful provenance, but it adds little about format expectations or mismatch handling. Baseline 3 applies for a fully documented two-parameter schema.

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?

The description states a concrete verb and resource — compare two designs and score similarity across palette, typography, shape and spacing — plus the added output of differentiation tips. It is unambiguous about what the operation produces. It does not, however, distinguish itself from the sibling 'compare_designs', which an agent could plausibly reach for instead.

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?

It gives clear upstream context: 'Pass the JSON from extract_tokens or analyze_design for each', and frames the use case as checking a recreation or reimagination against the source. That is actionable when-to-use guidance. There is no explicit when-not or statement of how it differs from compare_designs, so it stops short of a full routing rule.

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