Skip to main content
Glama

Better Design

by io.github.marvkr
OverviewDiscussionsAdmin

Get Inspiration

get-inspiration
Read-onlyIdempotent

Returns real reference designs from Better Design's library. type picks the collection: app-screens, product screens of shipped apps as images, found by words in query such as "settings" and an optional platform; html-flows, shipped web flows rebuilt as HTML, found by words in query; or app-store-screenshots, App Store screenshot sets as images, narrowed by an App Store category. limit sets how many come back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesThe kind of reference to send: "app-screens", "html-flows" or "app-store-screenshots".
limitNoHow many sets or flows to send. Defaults to 3 sets or 2 flows; at most 6 sets or 3 flows.
queryNoFor app-screens and html-flows: words matched against flow names, such as "settings" or "invite team".
categoryNoFor app-store-screenshots only: an App Store category such as "Productivity". Ignores case.
platformNoFor app-screens only: "ios", "android" or "web".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional App Store category, for example \"Productivity\" or \"Health & Fitness\". Ignores case."New value: +"For app-store-screenshots only: an App Store category such as \"Productivity\". Ignores case."
    • changedInput schema / properties / limit / description
      Previous value: -"How many sets to send, 1 to 6. Defaults to 3."New value: +"How many sets or flows to send. Defaults to 3 sets or 2 flows; at most 6 sets or 3 flows."
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "For app-screens only: \"ios\", \"android\" or \"web\".",
+  "enum": [
+    "ios",
+    "android",
+    "web"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "For app-screens and html-flows: words matched against flow names, such as \"settings\" or \"invite team\".",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / type / description
      Previous value: -"The kind of reference to send. Today: \"app-store-screenshots\"."New value: +"The kind of reference to send: \"app-screens\", \"html-flows\" or \"app-store-screenshots\"."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "app-store-screenshots"
-]New value: +[
+  "app-store-screenshots",
+  "app-screens",
+  "html-flows"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. Beyond that, the description discloses the output form per collection (images, rebuilt HTML flows, screenshot sets) and the matching mechanism (word matches against flow names), which is real behavioral value not in the annotations. No rate limits or auth context, so not a 5.

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?

A single dense paragraph, front-loaded with the core purpose before the per-type breakdown. It is efficient and every clause earns its place, though the run-on structure packs a lot into one sentence.

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 no output schema, the description must carry return-value expectations, and it does so qualitatively for each type (images vs HTML flows vs screenshot sets). Combined with the 100%-covered schema, an agent has enough to invoke correctly, though concrete shape/count details of results are left implicit.

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 100%, so the baseline is 3, but the description adds cross-parameter relationships the schema states only per-field: that `platform` is app-screens-only, `category` is app-store-screenshots-only, and `query` applies to app-screens and html-flows. This mapping genuinely helps an agent combine parameters correctly.

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 ('returns real reference designs from Better Design's library') and then enumerates the three collections selectable via `type`, each with its own characterization. An agent can tell it apart from the many sibling 'get-*' guide tools, which return guidance rather than reference designs.

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?

Explains how to select each `type` and which narrowing parameter (`query`, `platform`, `category`) accompanies it, giving clear selection context. It stops short of stating when to prefer this over alternatives or any exclusions, so it falls short of the explicit when/when-not bar.

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

All Better Design 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