Skip to main content
Glama

Designesy

by io.github.LE-VAI
OverviewDiscussionsAdmin

Get design contract

designesy_contract
Read-onlyIdempotent

Get the Designesy design-system contract: the canonical tokens, motion, acoustic, takt, cadence, typography, components, and verification rules that define what the Designesy org considers legitimate design. Use this when you need the actual contract values (token names and values, motion timings, accessibility rules) to author, check, or bind a design. When NOT to use: for a pass/fail score of a live site, use designesy_score; for an agent-skill-format export, use designesy_skill_md. Read-only; this server caches the fetched contract for 5 minutes. With no arguments it returns the full contract JSON, about 125 KB (roughly 31k tokens). To return less, pass sections, a list of top-level keys such as ["motion", "colors"]: the result holds id, version, and only those keys. section (one name) is the older form and returns { section, data }. An unknown name returns an error that lists every valid key.

Input Schema

NameRequiredDescriptionDefault
sectionNoOptional, older form: one top-level key; returns { section, data }. Prefer sections.
sectionsNoOptional: top-level contract keys to return. The result holds id, version, and only these keys. Omit for the full contract. Valid keys: id, version, status, name, public_url, full_contract_url, machine_url, updated, schema_hints, provenance, colors, surfaces_and_lines, shadows, materials, rounded, layout, motion, interaction, takt, cadence, typography, acoustic, semantic, copywriting, components, accessibility, anti_patterns, implementation, verification, verification_checks, open_tensions, adoption_history, promotion_candidates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / section / description
      Previous value: -"Optional: filter to a specific contract section (colors, motion, acoustic, typography, takt, cadence, verification, verification_checks, open_tensions, components, interaction)."New value: +"Optional, older form: one top-level key; returns { section, data }. Prefer sections."
    • addedInput schema / properties / sections
      Added value: +{
+  "description": "Optional: top-level contract keys to return. The result holds id, version, and only these keys. Omit for the full contract. Valid keys: id, version, status, name, public_url, full_contract_url, machine_url, updated, schema_hints, provenance, colors, surfaces_and_lines, shadows, materials, rounded, layout, motion, interaction, takt, cadence, typography, acoustic, semantic, copywriting, components, accessibility, anti_patterns, implementation, verification, verification_checks, open_tensions, adoption_history, promotion_candidates.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Optional: filter to a specific contract section (colors, motion, acoustic, typography, takt, cadence, verification, open_tensions, components, interaction)."New value: +"Optional: filter to a specific contract section (colors, motion, acoustic, typography, takt, cadence, verification, verification_checks, open_tensions, components, interaction)."
  3. Changed2 schema fields changed
    • 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
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds non-obvious operational traits: a 5-minute server-side cache of the fetched contract, the default response size (~125 KB / ~31k tokens), and that unknown names produce an error listing every valid key.

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?

Front-loaded with purpose, then usage, then parameter behavior; each sentence carries information. It is somewhat long and re-enumerates the top-level keys that the schema already lists, but that redundancy is minor.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by describing the exact response shape for both parameter forms, the default full-contract payload, and the caching behavior — nothing an agent needs to call this correctly is missing.

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 already 100%, so the baseline is 3, but the description adds return-shape semantics the schema does not: sections yields {id, version, ...keys} while the older section yields {section, data}, plus the error behavior for unknown names.

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 ('Get the Designesy design-system contract') and then enumerates the contents (tokens, motion, acoustic, takt, typography, components, verification rules), which makes it trivially distinguishable from siblings like designesy_score or designesy_skill_md.

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 an explicit positive trigger ('when you need the actual contract values ... to author, check, or bind a design') and an explicit negative trigger routed to named alternatives: designesy_score for pass/fail, designesy_skill_md for skill-format export.

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

All Designesy toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources