Offline Designer MCP

Overview Schema Source Related Servers Discussions Admin

designer_get_reference

Read-onlyIdempotent

Retrieve a local UI or design reference with guidance, examples, assets, and source/license citations to inform implementation without network access.

Instructions

Read a local UI/design reference with guidance, examples, assets and source/license citations.

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": {
      "id": "<id>"
    },
    "name": "designer_get_reference"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that the returned reference bundles guidance, examples, assets and license/source citations, but says nothing about behavior when the id is unknown or unlicensed.

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?

One front-loaded sentence with no filler; the verb and resource lead. The trailing noun list of contents is dense but each item conveys what the agent will receive.

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

Completeness3/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 shape need not be explained, and the annotations cover safety. However, for a by-id lookup the omission of how to obtain a valid id and what happens on a missing id leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'id' has 0% schema description coverage, so the schema gives no meaning, and the description does not explain what an id identifies, where ids come from, or whether they are discoverable via designer_search. The 1-120 length bound is the only hint.

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?

States a specific verb (Read) and resource (a local UI/design reference) and enumerates what the reference contains (guidance, examples, assets, citations). An agent can distinguish it from designer_search as a by-id retrieval rather than a lookup, though the description never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the word 'local' and the singular reference suggest fetching a known item by id, as opposed to the sibling designer_search or designer_get_bundle. There is no explicit when-to-use, when-not-to-use, or fallback guidance.

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

Deploy Server