Reflex Docs MCP Server

get_component_props

Retrieve the props table for any Reflex component, with optional filtering to match prop names or descriptions.

Instructions

Get the props table for a specific Reflex component.

Args: name: Component name (e.g., "rx.button", "button"). The "rx." prefix is optional. filter: Optional filter string to match prop names or descriptions

Returns: Dict with component name, total props count, and filtered props list

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "get_component_props"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`filter`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 14, 2026

TDQS

A4/5.0

Behavior3/5

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

Describes return format (dict with specific fields) but does not disclose error behavior (e.g., missing component) or confirm read-only nature. No annotations provided to cover these gaps.

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?

Well-structured with args/returns sections, front-loaded purpose, but slightly verbose for a tool description. Could be more concise without losing clarity.

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?

Covers purpose, both parameters, and return format. Lacks error handling details, but for a read-like tool with simple parameters, it is fairly complete. Output schema exists, reducing burden on description.

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

Parameters5/5

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

Adds significant meaning beyond the schema: explains 'name' accepts optional 'rx.' prefix and 'filter' matches prop names/descriptions. Schema has 0% description coverage, so description fully compensates.

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?

Explicitly states it retrieves the props table for a Reflex component. Differentiates from sibling tools like 'get_component' which likely returns full component details, and 'list_components' which lists components.

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

Usage Guidelines3/5

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

Provides examples for the 'name' parameter and optional 'filter', but does not explicitly state when to use this tool over alternatives like 'get_component' or 'search_components'. Implied usage from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server