Skip to main content
Glama

Get a DIYA component

get_component
Read-onlyIdempotent

Everything needed to use one DIYA component or pattern correctly: import, props with types and defaults, content slots, controlled and uncontrolled state, the types its props use, accessibility, and a complete .tsx file that type-checks.

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_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExport name, title or catalog id: "Switch", "Side Navigation", "text-input"
includeNoSections to return; props, accessibility and example if left out

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the safe, idempotent, closed-world read profile, so the description's job is to describe the payload — and it does, promising a complete .tsx file that type-checks plus accessibility and controlled/uncontrolled state details. It stops short of describing error behavior or how the response is structured.

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?

A single dense sentence that front-loads the value proposition and then lists return contents efficiently. It is a slight cost that the actual action is buried in a benefit statement rather than leading with the verb.

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

Completeness4/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 carries the return-value burden and discharges it by naming each section an agent can expect. The remaining gaps — mapping of the include values to those sections and failure modes for unknown names — are minor for a two-parameter read tool.

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%, with the name format and the include enum fully documented, so the baseline is 3. The description adds no parameter meaning, and its 'everything needed' framing is slightly at odds with the schema's default of only props, accessibility, and example.

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 plus title make clear this retrieves the full usage documentation for a single named DIYA component or pattern, and it enumerates exactly what comes back (import, props, state, accessibility, .tsx). It doesn't explicitly contrast with search_components, so sibling differentiation is left implicit.

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 implied by the phrase 'to use one DIYA component or pattern correctly' and by the schema's note that name accepts an export name, title, or catalog id. There is no explicit when-to-use statement, no mention of searching first when the component name is unknown, and no stated behavior for a missing component.

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.

Resources