Skip to main content
Glama
lmn451

JSX Prop Lookup MCP Server

by lmn451

get_component_props

Retrieve all props used by a specific React component, including types and default values, to document component APIs and verify prop usage.

Instructions

Get detailed information about all props used by a specific component.

Use this tool when you need to:

  • Understand what props a component accepts and uses

  • Document component APIs

  • Check if a component has certain props before using it

  • Analyze component interfaces

EXAMPLES:

  1. Get all props for Button component in current directory: { "componentName": "Button" }

  2. Check Modal component props in specific directory: { "componentName": "Modal", "directory": "src/components" }

  3. Document Card component API in UI directory: { "componentName": "Card", "directory": "src/ui" }

  4. Analyze Input component interface in current directory: { "componentName": "Input" }

Returns:

  • All props used by the component

  • Prop types and default values

  • Usage statistics across the codebase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentNameYesName of the component to analyze (e.g., "Button", "Modal", "Card")
directoryNoDirectory to search in (defaults to current directory).
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It mentions the tool returns props, types, defaults, and usage statistics, but does not disclose if it scans recursively, performance implications, or error handling (e.g., missing component). Safe read-only behavior is implied but not stated.

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 clear purpose statement, usage bullets, examples, and a return summary. It is front-loaded and each section earns its place. The examples are helpful but could be slightly condensed.

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?

Despite lacking an output schema, the description adequately describes the return values (all props, types, defaults, usage statistics). It covers essential information for a simple analysis tool. Missing details about error states or edge cases prevent a higher score.

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 coverage is 100%, so both parameters (componentName, directory) are described. The description adds examples showing real usage but does not provide additional semantic meaning beyond the schema. Baseline score of 3 is appropriate.

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 specifies the tool retrieves detailed prop information for a component, including types, defaults, and usage statistics. The verb 'get' and resource 'component props' are explicit, and the examples reinforce the purpose. It distinguishes from siblings like find_prop_usage and find_components_without_prop by focusing on complete prop details.

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 concrete use cases (e.g., understand props, document APIs, check before using) which guide the agent effectively. However, it does not explicitly state when not to use this tool or mention direct alternatives, which slightly limits guidance completeness.

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