Skip to main content
Glama
Sign In
design-copier

design-copier

by chipsxp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

designcopier_apply

Generate a component by applying extracted styles to React, Vue, Angular, or Svelte. Provide styles, framework, and component name.

Instructions

Apply extracted styles to target framework

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": {
      "styles": "<styles>",
      "targetFramework": "<targetFramework>",
      "componentName": "<componentName>"
    },
    "name": "designcopier_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
stylesYesExtracted styles
targetFrameworkYesTarget framework
componentNameYesName for the generated component

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so description carries full burden. It only says 'Apply extracted styles' without disclosing any side effects, permissions, or output behavior. Important for a code generation tool.

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

Conciseness2/5

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

Extremely brief (one short sentence) but underspecified. Conciseness at the cost of completeness is not effective.

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

Completeness2/5

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

Missing context on output format, interaction with sibling tools, and practical usage steps. Schema covers params but not tool behavior.

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 description coverage is 100%, so the schema already documents each parameter. The description adds no additional meaning beyond what is in the 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?

Description states 'Apply extracted styles to target framework' which clearly indicates the action (apply) and the resource (styles) and target. It distinguishes from sibling 'designcopier_extract' (which likely extracts) but does not differentiate from 'designcopier_snapshot'.

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

Usage Guidelines2/5

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

No usage guidance provided. Does not indicate when to use this tool versus alternatives, nor any prerequisites (e.g., need to extract styles first).

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

Deploy Server

Other Tools