MCP-RQuest
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| http_getC | Make an HTTP GET request to the specified URL |
| http_postC | Make an HTTP POST request to the specified URL |
| http_putC | Make an HTTP PUT request to the specified URL |
| http_deleteC | Make an HTTP DELETE request to the specified URL |
| http_patchA | Make an HTTP PATCH request to the specified URL |
| http_headC | Make an HTTP HEAD request to retrieve only headers from the specified URL |
| http_optionsC | Make an HTTP OPTIONS request to retrieve options for the specified URL |
| http_traceA | Make an HTTP TRACE request for diagnostic tracing of the specified URL |
| get_stored_responseC | Retrieve a stored HTTP response by its ID |
| get_stored_response_with_markdownA | Retrieve a stored HTTP response by its ID and convert it to Markdown format. Supports HTML and PDF content types. (Converting large PDF to Markdown may cause timeout, just wait and try again.) |
| get_model_stateB | Get the current state of the PDF models(used by |
| restart_model_loadingA | Restart the PDF models(used by |
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 12 tools
The HTTP method tools are clearly distinct, and the two stored response tools are differentiated by markdown conversion. However, get_stored_response and get_stored_response_with_markdown could be confused by an agent without careful reading, but descriptions mitigate ambiguity.
All tool names follow a consistent snake_case verb_noun pattern, with http_ prefix for HTTP methods and clear action words like get, restart, and retrieve. The naming is highly predictable and uniform.
12 tools is well-scoped for an HTTP client with model management and stored response retrieval. Each tool has a clear purpose, and the count is neither sparse nor overwhelming.
The HTTP methods cover all standard request types, and stored response handling is present. Minor gaps include no tool to clear or list stored responses, and model state tools are limited to get and restart, but core functionality is complete.