Reflex Docs MCP Server

get_code_examples

Retrieve Python code examples from Reflex documentation for any topic. Includes code snippets and source information to assist development.

Instructions

Find Python code examples from Reflex docs related to a topic.

Args: topic: Topic to search for (e.g., "state vars", "event handlers") limit: Maximum number of code examples to return (default: 5)

Returns: Dict with topic, count, and list of code examples with source info

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": {
      "topic": "<topic>"
    },
    "name": "get_code_examples"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	Yes
`limit`	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.2/5.0

Behavior4/5

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

Discloses return format (dict with topic, count, list of examples) and source info. No annotations provided, so description carries full burden; it describes side-effect-free read operation adequately.

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?

Single sentence for purpose, followed by clean bullet list for parameters. No redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter tool with output schema, description covers what the tool does, parameters, and return format. No gaps.

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?

Schema coverage is 0%, but description compensates fully by explaining each parameter: topic with examples, limit with meaning and default. Adds value beyond schema.

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?

Clear verb 'Find' and specific resource 'Python code examples from Reflex docs' differentiate from siblings like 'get_doc' or 'search_docs' which return full documentation.

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?

No guidance on when to use this tool versus alternatives (e.g., search_api_reference, search_docs). Agent must infer from name, which may lead to incorrect selection.

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

Deploy Server