Skip to main content
Glama

get_specification

Retrieve comprehensive UI component specification documentation to understand modern component-building philosophy, patterns, and best practices for creating accessible, framework-agnostic interfaces.

Instructions

Get the FULL components.build specification documentation. This is the complete guide to building modern UI components by Hayden Bleasel and shadcn. Use this to understand the complete philosophy, patterns, and best practices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoSpecific section to retrieve (optional). Available sections: overview, definitions, principles, composition, accessibility, designTokens, state, styling, types, polymorphism, asChild, dataAttributes, docs, registry, marketplaces, npm

Implementation Reference

  • The handler function that implements the core logic of the 'get_specification' tool. It processes input arguments to retrieve either a specific section or the full specification using imported utility functions and formats the response as a ToolResult.
    function handleGetSpecification(args: Record<string, unknown>): ToolResult {
      const section = args.section as string | undefined;
    
      if (section) {
        const content = getSection(section);
        if (!content) {
          return {
            content: [
              {
                type: 'text',
                text: `Section not found: ${section}\n\nAvailable sections:\n${getSectionNames()
                  .map((s) => `- ${s}`)
                  .join('\n')}`,
              },
            ],
            isError: true,
          };
        }
        return {
          content: [{ type: 'text', text: content }],
        };
      }
    
      // Return the full specification
      return {
        content: [{ type: 'text', text: getFullSpecification() }],
      };
    }
  • The tool definition including name, description, and input schema for validating parameters (optional 'section' string). Part of the getToolDefinitions() array used for tool registration.
    {
      name: 'get_specification',
      description: 'Get the FULL components.build specification documentation. This is the complete guide to building modern UI components by Hayden Bleasel and shadcn. Use this to understand the complete philosophy, patterns, and best practices.',
      inputSchema: {
        type: 'object',
        properties: {
          section: {
            type: 'string',
            description: 'Specific section to retrieve (optional). Available sections: overview, definitions, principles, composition, accessibility, designTokens, state, styling, types, polymorphism, asChild, dataAttributes, docs, registry, marketplaces, npm',
          },
        },
      },
    },
  • The dispatch case in the executeTool switch statement that routes calls to the 'get_specification' handler.
    case 'get_specification':
      return handleGetSpecification(args);
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. It mentions retrieving 'FULL' documentation and that it's 'complete', which hints at comprehensiveness, but doesn't disclose behavioral traits such as response format, pagination, error handling, or performance considerations. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 concise and front-loaded, with two sentences that efficiently convey the tool's purpose and intended use. Every sentence adds value, though it could be slightly more structured by explicitly separating purpose from usage context.

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 tool has no annotations, no output schema, and a simple input schema, the description is adequate but incomplete. It covers the purpose and high-level context but lacks details on behavior, output format, or error handling, which are important for a documentation retrieval tool. It's minimally viable but has clear gaps.

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?

The input schema has 100% description coverage, with the 'section' parameter well-documented including optional status and available values. The description adds no parameter-specific information beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without compensating with additional semantics.

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 clearly states the tool's purpose: 'Get the FULL components.build specification documentation' and identifies it as 'the complete guide to building modern UI components'. It specifies the resource (specification documentation) and verb (get), though it doesn't explicitly differentiate from sibling tools like 'get_quick_reference' or 'list_specification_sections'.

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?

The description implies usage context by stating this is for 'understanding the complete philosophy, patterns, and best practices', suggesting it's comprehensive. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_quick_reference' or 'list_specification_sections', nor does it provide any exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/getlokiui/components-build-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server