tdrest
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELASTIC_COMPUTE_BASE_URL | No | Base URL for the Elastic Compute API |
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 |
|---|---|
| list_filesB | List files in a directory with optional filtering by extension |
| find_filesA | Find files matching a glob pattern (e.g., /tmp/.pdf, ~/Documents/**/.csv) |
| get_service_configA | Get configured service base URLs (Elastic Compute, Vector Store, timeouts, etc.) |
| execute_rest_callA | Execute a REST API call with support for custom auth, Socks5 proxy, and multipart uploads. Use get_service_config to see available base URLs. |
| set_authB | Set session-level authentication for subsequent requests |
| set_proxyB | Set session-level proxy for subsequent requests |
| get_syntax_helpB | Get help and syntax for available API endpoints from Swagger specs |
| get_usage_guideA | Get usage guides with best practices, workflows, and examples for APIs |
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 8 tools
Tools are mostly distinct: REST execution, configuration, help, and file operations. Some overlap between find_files and list_files, and between get_syntax_help and get_usage_guide, but descriptions help differentiate.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., execute_rest_call, find_files, get_service_config.
8 tools is well-scoped for a REST client utility, covering setup, execution, help, and file discovery without being excessive.
Covers key aspects of REST API interaction: auth, proxy, execution, config, and help. Missing maybe a tool to clear credentials or inspect raw responses, but core workflow is supported.