Skip to main content
Glama
lmn451

JSX Prop Lookup MCP Server

by lmn451

find_components_without_prop

Find component instances missing a required prop to audit accessibility, styling, or other prop requirements.

Instructions

Find component instances that are missing a required prop (e.g., Select components without width prop).

Use this tool when you need to:

  • Audit components for missing required props

  • Ensure accessibility props are present (e.g., missing aria-label)

  • Check for missing styling props (e.g., missing width or height)

  • Enforce prop requirements across the codebase

  • Refactor components and ensure all usages are updated

EXAMPLES:

  1. Find Select components missing width prop in current directory: { "componentName": "Select", "requiredProp": "width" }

  2. Audit Image components for missing alt text in current directory: { "componentName": "Image", "requiredProp": "alt" }

  3. Find Button components missing type prop in src directory: { "componentName": "Button", "requiredProp": "type", "directory": "src" }

  4. Check Input components for missing label in forms directory: { "componentName": "Input", "requiredProp": "aria-label", "directory": "src/forms" }

Returns:

  • List of component instances missing the required prop

  • File paths and line numbers

  • Existing props on those instances

  • Summary statistics (total instances vs missing count)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentNameYesName of the component to check (e.g., "Select", "Button", "Image")
requiredPropYesName of the required prop that should be present (e.g., "width", "alt", "aria-label")
directoryNoDirectory to search in (defaults to current directory).
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 specifies return values (list, file paths, line numbers) but lacks critical behavioral details like file types scanned, recursion behavior, performance implications, or error handling.

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 well-structured with sections for purpose, use cases, examples, and returns. It is appropriately sized and front-loaded, though some information is slightly redundant (e.g., repeating purpose in examples).

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?

For a relatively simple tool, the description covers the main aspects: purpose, parameters (via examples), and return format. It is missing potential edge cases but overall is complete enough given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions. The description adds value with concrete examples (e.g., 'Select components without width prop') and usage patterns that go beyond what the schema alone provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the purpose with a specific verb 'Find component instances that are missing a required prop', and it is easily distinguished from siblings like 'analyze_jsx_props' and 'find_prop_usage' which focus on different aspects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a dedicated 'Use this tool when you need to' section with five explicit tasks, providing clear context. However, it does not mention when not to use it or explicitly compare to siblings, so it loses the top score.

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/lmn451/jsx-prop-lookup-mcp-server'

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