Get Page
get-pageReads a docs page as markdown, whole or just the sections you name. Component pages explain why each rule exists, with examples in React, Vue, Svelte, Angular, Solid, Astro and Vanilla: pass a framework to keep only its examples.
WHEN TO USE: for the reasoning, an example or the details behind a rule (like the sections ["Loading"] of the button's page), or for a page without a contract, like the introduction or the roadmap. WHEN NOT TO USE: for the requirements alone, use get-contract or list-rules, which are much shorter. To find which page or section covers a topic, use search-docs.
A page longer than about 8,000 tokens, like the button's, returns its outline instead: every heading with its anchor and length, so you can ask for the sections you need. So do sections that are too long to return together.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The page: its name (introduction, roadmap, mcp-server, agent-plugin, design-tokens, button, card, checkbox-group, checkbox, dialog, field, input, popover, radio-group, spinner, switch, textarea, tooltip), or its path, like /docs/components/button. A URL's #anchor, like the ones search-docs returns, reads that section. | |
| sections | No | The sections to read, by heading or anchor, like ["Loading"] or ["#ux-rules"]. Each comes with its sub-sections. Name a parent to tell apart headings that repeat, as in "Every state > Loading". | |
| framework | No | Your framework, to keep only its examples. |