Skip to main content
Glama

Get a UI component

get_component
Read-onlyIdempotent

Get metadata, the design specification, source references and the available implementations of one component by id.

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": "get_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesComponent id from search_components.
versionNoConcrete version or latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description still adds genuine value by disclosing what the response contains (metadata, design spec, source references, implementations), which matters because no output schema exists. It does not mention behavior on an unknown id or how an omitted version is resolved.

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?

A single front-loaded sentence with the verb first and the returned content enumerated compactly; there is no filler or redundancy.

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?

Because there is no output schema, enumerating returned fields is the right compensating move, and annotations cover safety. Remaining gap is the relationship to the sibling tools and error behavior on a missing component.

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%, so both parameters are already documented, including that id comes from search_components and version accepts 'latest'. The description adds 'by id' and the notion of multiple available implementations, but says nothing about version selection semantics beyond what the schema supplies.

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 (Get) and resource (one component by id) and enumerates the payload: metadata, design specification, source references, implementations. That distinguishes it from search_components (listing) but leaves the boundary with get_component_code ('available implementations' vs 'code') unstated.

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 by 'by id' and the sibling-named schema field 'Component id from search_components'. There is no explicit statement of when to prefer this over search_components or get_component_code, nor any prerequisite or not-found guidance.

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