rndocs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_react_native_docsA | Search React Native documentation by keyword or concept. Args: query: Search terms (e.g. 'FlatList', 'navigation', 'StyleSheet flex') limit: Maximum number of results to return (default 10) |
| get_react_native_docA | Get the full content of a React Native doc page by its slug. Args: slug: The doc page slug (e.g. 'flatlist', 'animated', 'getting-started', 'stylesheet') Find slugs using search_react_native_docs first. |
| list_react_native_docsA | List all available React Native doc pages, optionally filtered by section. Args: section: Filter by section name (e.g. 'Components', 'APIs', 'Guides'). Leave empty for all. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: retrieving a specific doc by slug, listing all docs (optionally filtered), and searching by keyword. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (get_react_native_doc, list_react_native_docs, search_react_native_docs), with singular/plural matching the operation.
Three tools is appropriate for a focused documentation server. Each tool serves a necessary function without redundancy, and the count is not too small or excessive.
The tool set covers the essential workflow: discover pages (list and search) and retrieve full content (get). No obvious gaps exist for the stated purpose of accessing React Native docs.