Skip to main content
Glama
stephenlumban

NTV Scaffolding MCP Server

get_ntv_component_props

Retrieve detailed input properties and configuration options for Angular components to understand component capabilities and usage requirements.

Instructions

Get detailed information about a component's input properties and configuration options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentYesComponent name (e.g., 'Button', 'Input')
propNameNoOptional: Get details for a specific property

Implementation Reference

  • The execute function implementing the tool's core logic: retrieves the component from COMPONENTS_DB by name, optionally filters by propName, and returns property details or all properties with configInterface.
    execute: async (args: Record<string, unknown>) => {
      const componentName = args.component as string;
      const propName = args.propName as string | undefined;
    
      const component = COMPONENTS_DB.find(
        (c) => c.name.toLowerCase() === componentName.toLowerCase()
      );
    
      if (!component) {
        throw new Error(`Component '${componentName}' not found`);
      }
    
      if (propName) {
        const prop = component.props.find(
          (p) => p.name.toLowerCase() === propName.toLowerCase()
        );
        if (!prop) {
          throw new Error(
            `Property '${propName}' not found on component '${componentName}'`
          );
        }
        return { component: componentName, property: prop };
      }
    
      return {
        component: componentName,
        properties: component.props,
        configInterface: component.configInterface || null,
      };
    },
  • Input schema defining the expected arguments: required 'component' string and optional 'propName' string.
    inputSchema: {
      type: "object",
      properties: {
        component: {
          type: "string",
          description: "Component name (e.g., 'Button', 'Input')",
        },
        propName: {
          type: "string",
          description: "Optional: Get details for a specific property",
        },
      },
      required: ["component"],
    },
  • Registers the tool (imported as getComponentPropsToolDefinition from getComponentProps.js) in the central componentTools array used for MCP tool exposure.
    export const componentTools: MCPTool[] = [
      generateComponentTool,
      getComponentDocTool,
      listComponentsTool,
      generateComponentUsageTool,
      getComponentPropsToolDefinition,
      generateTemplateCodeTool,
      getComponentExamplesTool,
      getComponentUsagePatternTool,
    ];
  • Defines and exports the complete MCPTool object for 'get_ntv_component_props', including name, description, schema, and handler.
    export const getComponentPropsToolDefinition: MCPTool = {
      name: "get_ntv_component_props",
      description:
        "Get detailed information about a component's input properties and configuration options",
      inputSchema: {
        type: "object",
        properties: {
          component: {
            type: "string",
            description: "Component name (e.g., 'Button', 'Input')",
          },
          propName: {
            type: "string",
            description: "Optional: Get details for a specific property",
          },
        },
        required: ["component"],
      },
      execute: async (args: Record<string, unknown>) => {
        const componentName = args.component as string;
        const propName = args.propName as string | undefined;
    
        const component = COMPONENTS_DB.find(
          (c) => c.name.toLowerCase() === componentName.toLowerCase()
        );
    
        if (!component) {
          throw new Error(`Component '${componentName}' not found`);
        }
    
        if (propName) {
          const prop = component.props.find(
            (p) => p.name.toLowerCase() === propName.toLowerCase()
          );
          if (!prop) {
            throw new Error(
              `Property '${propName}' not found on component '${componentName}'`
            );
          }
          return { component: componentName, property: prop };
        }
    
        return {
          component: componentName,
          properties: component.props,
          configInterface: component.configInterface || null,
        };
      },
    };
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 describes a read operation ('Get detailed information'), which implies it's non-destructive, but doesn't disclose behavioral traits like authentication needs, rate limits, error conditions, or response format. The description is minimal and lacks context beyond the basic operation.

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 unnecessary words. It is appropriately sized and front-loaded, with every part contributing to understanding the tool's function.

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 no annotations, no output schema, and a read operation with 2 parameters, the description is incomplete. It doesn't explain what 'detailed information' includes, how results are structured, or any limitations. For a tool with siblings and potential complexity, 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%, so the schema already documents both parameters ('component' and 'propName') with descriptions. The description adds no additional meaning beyond what the schema provides, such as examples of property details or configuration options. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Get') and resource ('detailed information about a component's input properties and configuration options'). It distinguishes itself from siblings like 'get_ntv_component_doc' or 'get_ntv_component_examples' by focusing on properties/configuration, but doesn't explicitly contrast them.

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 like 'get_ntv_component_doc' or 'list_ntv_components'. It mentions an optional parameter but doesn't explain scenarios for using it or prerequisites for tool invocation.

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