Reflex Docs MCP Server

get_doc

Retrieve a full documentation page by its slug, with an option to extract only code blocks.

Instructions

Retrieve a full documentation page by its slug.

Args: slug: Document slug (e.g., "library/layout/box", "components/rendering_iterables") extract_code: If True, return only fenced code blocks from the page

Returns: Full document with title, URL, and all sections with markdown content

Example: get_doc("library/layout/box") get_doc("state/overview", extract_code=True)

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": {
      "slug": "<slug>"
    },
    "name": "get_doc"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`extract_code`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 14, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Despite no annotations, the description discloses the return structure (title, URL, sections with markdown content) and the behavioral change with 'extract_code'. It omits any mention of authentication, rate limits, or error handling, but these are not critical for a read-only retrieval tool.

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?

The description is concise and well-organized with clear sections (summary, args, returns, example). Every sentence contributes meaning without redundancy.

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?

Given the tool's simplicity, presence of an output schema, and clear description of return values, the definition is complete. It covers what the tool does, its parameters, and typical usage.

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?

The description adds significant value beyond the input schema by providing concrete examples for 'slug' and explaining the purpose of 'extract_code' ('return only fenced code blocks'). This fully compensates for the 0% schema coverage.

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 action ('Retrieve') and resource ('full documentation page by its slug'), making the tool's purpose immediately apparent. It distinguishes from sibling tools like 'list_components' and 'search_docs' by focusing on single-page retrieval.

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 provides practical usage examples and explains the effect of the optional 'extract_code' parameter. However, it does not explicitly state when to use this tool versus alternatives, nor does it offer exclusion criteria.

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

Deploy Server