Skip to main content
Glama

Get Reference Implementation

get-reference-implementation
Read-onlyIdempotent

Returns a shipped component's reference implementation: a Vue 3 component that meets every rule in its checklist, the tests that prove it, the helpers it shares with other components and its theme tokens. The live examples on the site run on this code.

WHEN TO USE: to build a component that meets the standard, in Vue or by porting it and its tests to another framework, or to see how a rule is met in code. WHEN NOT TO USE: for the requirements, use get-contract. For how the component is used in another framework, use get-page with that 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": {
      "component": "<component>"
    },
    "name": "get-reference-implementation"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOnly these files, like ["Button.vue"] or ["Button.test.ts"]. Leave it out for every file.
componentYesA component with a reference implementation, like button.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "checkbox-group",
      -  "dialog",
      -  "field",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "select",
      -  "spinner",
      -  "switch",
      -  "tag",
      -  "tag-group",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "combobox",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "select",
      +  "spinner",
      +  "switch",
      +  "tag",
      +  "tag-group",
      +  "textarea",
      +  "tooltip"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "checkbox-group",
      -  "dialog",
      -  "field",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "select",
      -  "spinner",
      -  "switch",
      -  "tag",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "select",
      +  "spinner",
      +  "switch",
      +  "tag",
      +  "tag-group",
      +  "textarea",
      +  "tooltip"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "checkbox-group",
      -  "dialog",
      -  "field",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "select",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "select",
      +  "spinner",
      +  "switch",
      +  "tag",
      +  "textarea",
      +  "tooltip"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "checkbox-group",
      -  "dialog",
      -  "field",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "select",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "checkbox-group",
      -  "dialog",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "checkbox-group",
      -  "dialog",
      -  "input",
      -  "radio-group",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "dialog",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "checkbox-group",
      -  "dialog",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "dialog",
      +  "input",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "checkbox-group",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "dialog",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  9. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "checkbox-group",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  10. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "card",
      -  "checkbox",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  11. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "card",
      +  "checkbox",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "tooltip"
      +]
  12. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "input",
      -  "spinner",
      -  "tooltip"
      -]New value: +[
      +  "button",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "tooltip"
      +]
  13. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "button",
      -  "input",
      -  "spinner"
      -]New value: +[
      +  "button",
      +  "input",
      +  "spinner",
      +  "tooltip"
      +]
  14. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish this as a safe, idempotent, closed-world read, so the description's remaining burden is low and it still adds real context: what the payload contains and the provenance claim that the site's live examples run on this exact code. It does not discuss response size or shape for components with many files, which is the only gap.

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?

Front-loaded with the definition, then two clearly labelled routing blocks. Every sentence carries information, and the closing note about live examples is one clause rather than a paragraph of marketing.

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 must convey the return contents, and it does so precisely. Two parameters at full schema coverage plus complete sibling routing leave nothing an agent needs to call this 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 description coverage is 100% and the component enum is self-documenting, so the schema carries the parameter burden. The description only implicitly hints at the files filter by naming file categories (component, tests, helpers, tokens), and never addresses the `files` parameter or its 20-item cap directly – baseline 3 is appropriate.

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?

Opens with a specific verb and resource ('Returns a shipped component's reference implementation') and then enumerates the payload: the Vue 3 component, its tests, shared helpers, and theme tokens. That enumeration plus the explicit contrast with get-contract and get-page makes it unmistakable which sibling to pick.

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?

Uses explicit WHEN TO USE / WHEN NOT TO USE blocks, naming two concrete alternatives with the condition that selects each: get-contract for requirements, get-page for another framework's usage. It even covers the porting use case, so no inference is required.

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.