Skip to main content
Glama
stephenlumban

NTV Scaffolding MCP Server

get_ntv_component_examples

Retrieve predefined usage examples and code snippets for specific Angular components to understand implementation patterns and accelerate development.

Instructions

Gets predefined usage examples and code snippets for a specific component

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentYesComponent name (e.g., 'Button', 'Input')
includeCodeNoInclude full code snippets in response. Default: true

Implementation Reference

  • The execute function implementing the tool logic: finds the component in COMPONENTS_DB, retrieves and formats its examples based on the includeCode parameter, and returns structured data.
    execute: async (args: Record<string, unknown>) => {
      const componentName = args.component as string;
      const includeCode = args.includeCode !== false;
    
      const component = COMPONENTS_DB.find(
        (c) => c.name.toLowerCase() === componentName.toLowerCase()
      );
    
      if (!component) {
        throw new Error(`Component '${componentName}' not found`);
      }
    
      const examples = component.examples || [];
      const formattedExamples = examples.map((example: any) => ({
        title: example.title,
        description: example.description,
        template: includeCode ? example.template : undefined,
        component: includeCode ? example.component : undefined,
        notes: example.notes,
      }));
    
      return {
        component: componentName,
        exampleCount: formattedExamples.length,
        examples: formattedExamples,
      };
    },
  • Input schema defining the parameters: component (required string) and optional includeCode (boolean).
    inputSchema: {
      type: "object",
      properties: {
        component: {
          type: "string",
          description: "Component name (e.g., 'Button', 'Input')",
        },
        includeCode: {
          type: "boolean",
          description: "Include full code snippets in response. Default: true",
        },
      },
      required: ["component"],
    },
  • The getComponentExamplesTool is registered in the componentTools array, imported on line 7, which is used by the MCP server to list and call 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 the full burden of behavioral disclosure. It states the tool 'Gets' examples and snippets, implying a read-only operation, but does not disclose any behavioral traits such as rate limits, authentication needs, error handling, or what the response format looks like. This is a significant gap for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly, earning the highest score for conciseness.

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's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral aspects and usage context. Without an output schema, it does not explain return values, and with no annotations, it misses safety or operational hints, making it incomplete for optimal agent 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?

The input schema has 100% description coverage, clearly documenting both parameters ('component' and 'includeCode'). The description adds no additional meaning beyond what the schema provides, such as examples of component names beyond 'Button' and 'Input' or details on code snippet formats. With high schema coverage, the baseline score of 3 is appropriate.

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 with a specific verb ('Gets') and resource ('predefined usage examples and code snippets for a specific component'), making it easy to understand what it does. However, it does not explicitly differentiate from sibling tools like 'get_ntv_component_doc' or 'get_ntv_component_usage_pattern', which might have overlapping or similar functions, so it misses the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives, such as sibling tools like 'get_ntv_component_doc' or 'generate_ntv_component_usage'. It lacks explicit context, exclusions, or prerequisites, leaving the agent to infer usage based on the name and description alone.

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