Skip to main content
Glama
stephenlumban

NTV Scaffolding MCP Server

get_ntv_component_doc

Retrieve detailed documentation for NTV components including props, events, and usage patterns to understand component functionality and implementation requirements.

Instructions

Gets comprehensive documentation for a specific NTV component including props, events, and usage patterns

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentYesComponent name (e.g., 'Button', 'Input', 'Card', 'Autocomplete')

Implementation Reference

  • The main handler function that executes the tool: retrieves the component documentation from the COMPONENTS_DB based on the provided component name, formats it, and returns props, events, slots, examples, and best practices.
    execute: async (args: Record<string, unknown>) => {
      const componentName = args.component as string;
      const component = COMPONENTS_DB.find(
        (c) => c.name.toLowerCase() === componentName.toLowerCase()
      );
    
      if (!component) {
        throw new Error(`Component '${componentName}' not found`);
      }
    
      return {
        name: component.name,
        selector: component.selector,
        category: component.category,
        description: component.description,
        imports: `import { ${component.name} } from '@ntv-scaffolding/component-pantry';`,
        props: component.props,
        events: component.events || [],
        slots: component.slots || [],
        examples: component.examples || [],
        bestPractices: component.bestPractices || [],
      };
    },
  • Input schema specifying the required 'component' parameter as a string.
    inputSchema: {
      type: "object",
      properties: {
        component: {
          type: "string",
          description:
            "Component name (e.g., 'Button', 'Input', 'Card', 'Autocomplete')",
        },
      },
      required: ["component"],
    },
  • The tool is registered by being included in the exported componentTools array in index.ts (imported at line 2). This array collects all MCP tools.
    export const componentTools: MCPTool[] = [
      generateComponentTool,
      getComponentDocTool,
      listComponentsTool,
      generateComponentUsageTool,
      getComponentPropsToolDefinition,
      generateTemplateCodeTool,
      getComponentExamplesTool,
      getComponentUsagePatternTool,
    ];
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves documentation, implying a read-only operation, but doesn't disclose behavioral traits such as error handling, response format, whether it requires authentication, or any rate limits. The description is minimal and lacks critical operational context.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

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

Completeness2/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 incomplete. It lacks details on what the comprehensive documentation includes (e.g., format, structure), how it differs from sibling tools, and behavioral aspects like error cases. For a tool in a family with multiple similar tools, more context is needed to guide effective use.

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 parameter 'component' well-documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as examples of valid component names or constraints. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 action ('Gets') and resource ('comprehensive documentation for a specific NTV component'), specifying it includes props, events, and usage patterns. It distinguishes from some siblings like 'get_ntv_component_props' by being more comprehensive, but doesn't explicitly differentiate from all related tools like 'get_ntv_component_examples'.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for getting comprehensive documentation, but doesn't specify scenarios where this is preferred over siblings like 'get_ntv_component_examples' or 'get_ntv_component_props', nor does it mention prerequisites or exclusions.

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/stephenlumban/component-mcp'

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