http-prompt-reloaded
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 |
|---|---|
| http_prompt_initB | Initializes or updates a stateful HTTP exploration session. |
| http_prompt_cdB | Navigates the API URL path like a directory (e.g., 'cd /api/v1', 'cd users', 'cd ..'). |
| http_prompt_configureC | Sets persistent headers or query parameters for the session. |
| http_prompt_executeC | Executes an HTTP request on the current stateful path. |
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 4 tools
Each tool maps to a distinct action in the session lifecycle: init (create session), cd (navigate path), configure (set headers/params), execute (send request). There is mild overlap between init's 'updates' behavior and configure's session-state mutation, but the descriptions keep them largely separable.
All four tools share the same http_prompt_ prefix followed by a clear verb (execute, init, cd, configure). The pattern is fully predictable and easy to scan.
Four tools is a lean but sensible set for a stateful HTTP exploration shell, with each tool earning its place. It is slightly thin, as a few more session-management operations could reasonably fit.
The surface covers the core lifecycle: session init, path navigation, configuration, and request execution. Minor gaps exist around resetting/clearing session state or removing individual headers, but core workflows are fully supported.