Skip to main content
Glama
lmn451

JSX Prop Lookup MCP Server

by lmn451

find_prop_usage

Searches JSX files to find all instances where a given prop is used, helping audit usage and patterns.

Instructions

Find all usages of a specific prop across JSX/React files.

Use this tool when you need to:

  • Locate where a prop is used throughout the codebase

  • Find all components that use a specific prop like "onClick", "className", etc.

  • Audit prop usage for refactoring or deprecation

  • Understand prop propagation patterns

EXAMPLES:

  1. Find all onClick handlers in current directory: { "propName": "onClick" }

  2. Find className usage in components directory: { "propName": "className", "directory": "src/components" }

  3. Find variant prop only on Button components in current directory: { "propName": "variant", "componentName": "Button" }

  4. Find all disabled props in specific directory: { "propName": "disabled", "directory": "src/forms" }

Returns:

  • List of component instances using the prop

  • File paths and line numbers

  • Values passed to the prop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propNameYesName of the prop to search for (e.g., "onClick", "className", "variant")
directoryNoDirectory to search in (defaults to current directory).
componentNameNoFilter: only search within this component name (e.g., "Button")
Behavior4/5

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

No annotations provided, but the description explains that it returns file paths, line numbers, and values. It implies a read-only search operation without side effects. Could explicitly state read-only nature but overall good transparency.

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 a main sentence, bulleted use cases, examples in JSON, and return info. It is slightly verbose due to examples but they are directly useful.

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?

With 3 parameters and no output schema, the description covers usage, parameter behavior via examples, and return values. It adequately addresses the complexity and leaves no major gaps.

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 descriptions, but the description adds practical examples and clarifies default for directory and filtering role of componentName. This adds meaning beyond the schema alone.

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 starts with 'Find all usages of a specific prop across JSX/React files' which is a specific verb+resource combination. The examples and sibling tools (analyze_jsx_props, find_components_without_prop, get_component_props) show clear differentiation.

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 lists explicit use cases ('Locate where a prop is used', 'Audit prop usage') and provides examples. It does not state when not to use but the context is clear enough for an agent to decide.

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