Skip to main content
Glama
Sign In
Insider Design System MCP

Insider Design System MCP

by denizzeybek-fe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get-examples

Retrieve code examples for any Insider Design System component by component name. Find usage snippets to implement components correctly.

Instructions

Get code examples for using a component

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": {
      "name": "<name>"
    },
    "name": "get-examples"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesComponent name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool gets code examples; it does not disclose output format, behavior on unknown component names, or whether examples are fetched or generated. The word 'Get' weakly implies a read-only operation but nothing more.

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?

The description is a single, front-loaded sentence with no wasted words. For a tool with one parameter, this is appropriately concise, though it sacrifices useful detail.

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?

Given the low complexity of one parameter, the description is minimally adequate: an agent knows the tool returns code examples for a named component. However, with no output schema and no annotations, a bit more detail about the return format or example selection would make it fully complete.

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%, with the single 'name' parameter already described as 'Component name'. The tool description adds no meaningful parameter semantics beyond that, so the baseline of 3 applies.

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?

The description states a specific verb ('Get') and a clear resource ('code examples for using a component'). It is distinct enough from sibling tools like get-component or get-props, though it does not explicitly contrast itself with generate-code.

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?

There is no guidance about when to use this tool versus alternatives such as get-component, get-props, or generate-code. No exclusions, preconditions, or selection criteria are provided, leaving the agent to infer appropriateness from the name alone.

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