4D Documentation Viewer
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_4d_command_docsA | Get documentation for a 4D command. Fetches the documentation from https://developer.4d.com/docs/commands/ and extracts the article content from the main tag. Results are cached locally for faster subsequent access. |
| clear_4d_docs_cacheA | Clear the local cache of 4D documentation. This removes all cached documentation files, forcing fresh fetches on subsequent requests. |
| open_4d_command_in_browserA | Open a 4D command documentation page in the default web browser. This opens the URL https://developer.4d.com/docs/commands/ directly in your browser. |
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: clearing cache, fetching documentation content, and opening documentation in a browser. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern with '4d' as a prefix (clear_4d_docs_cache, get_4d_command_docs, open_4d_command_in_browser). The naming is uniform and predictable throughout the set.
With only 3 tools, the set feels thin for a documentation viewer that might benefit from additional operations like listing commands or searching documentation. However, it covers basic needs without being excessive.
The tools provide core functionality for accessing and managing 4D documentation (fetch, open, clear cache). Minor gaps exist, such as no tool for browsing or searching command lists, but agents can work around this by using the provided tools effectively.