Skip to main content
Glama

Get a design

get_design
Read-only

Returns one design from the NightMarquee library: its build prompt for the chosen coding tool, its live demo link and whether a starter project is available. Pass a brand name to have the prompt use it. Use it after search_designs, once you know which design you want. Free designs need no account; paid designs need a connected account with a plan.

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": {
      "slug": "<slug>"
    },
    "name": "get_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe design's slug, from search_designs.
toolNoThe coding tool the build prompt is written for. The default is claude.claude
brandNoA name for the site; it replaces the design's sample brand in the prompt. Up to 24 characters.

Output Schema

NameRequiredDescriptionDefault
kindYes
slugYes
tierYes
toolYes
stackYes
titleYes
promptYes
demoUrlYes
starterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the account/plan prerequisite for paid designs and the fact that the returned prompt is tailored to the selected coding tool. It stops short of describing error behavior or rate limits, so a 4 rather than 5.

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?

Three sentences, front-loaded with the return contents, then the parameter effect, then the sequencing and access rules. No filler and nothing repeated from the schema.

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?

An output schema exists, so return values need not be spelled out, and the description still summarizes them usefully. Combined with the sequencing guidance and the free/paid access rule, an agent has everything needed to decide and call correctly.

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 the baseline is 3, and the description does add effect-level meaning: the brand name replaces the design's sample brand inside the prompt, and the tool parameter determines which prompt variant is returned. However, it states the brand is 'Up to 24 characters' while the schema allows maxLength 200, a conflicting constraint that could mislead the agent.

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 one design from the NightMarquee library') and enumerates what comes back: build prompt for the chosen tool, live demo link, and starter-project availability. This is clearly distinguishable from search_designs, which is named as the discovery counterpart.

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?

Explicitly sequences the tool: 'Use it after search_designs, once you know which design you want,' which tells the agent both the precondition and the trigger. It also states the access condition (free designs need no account; paid designs need a connected account with a plan), so the agent knows when a call will fail.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.