HAL (HTTP API Layer)
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| http-getB | Make an HTTP GET request to a specified URL. Supports secret substitution using {secrets.key} syntax where 'key' corresponds to HAL_SECRET_KEY environment variables. |
| http-postA | Make an HTTP POST request to a specified URL with optional body and headers. Supports secret substitution using {secrets.key} syntax in URL, headers, and body where 'key' corresponds to HAL_SECRET_KEY environment variables. |
| http-putB | Make an HTTP PUT request to a specified URL with optional body and headers. Supports secret substitution using {secrets.key} syntax in URL, headers, and body where 'key' corresponds to HAL_SECRET_KEY environment variables. |
| http-patchB | Make an HTTP PATCH request to a specified URL with optional body and headers. Supports secret substitution using {secrets.key} syntax in URL, headers, and body where 'key' corresponds to HAL_SECRET_KEY environment variables. |
| http-deleteA | Make an HTTP DELETE request to a specified URL with optional headers. Supports secret substitution using {secrets.key} syntax in URL and headers where 'key' corresponds to HAL_SECRET_KEY environment variables. |
| http-headA | Make an HTTP HEAD request to a specified URL with optional headers (returns only headers, no body). Supports secret substitution using {secrets.key} syntax in URL and headers where 'key' corresponds to HAL_SECRET_KEY environment variables. |
| http-optionsA | Make an HTTP OPTIONS request to a specified URL to check available methods and headers. Supports secret substitution using {secrets.key} syntax in URL and headers where 'key' corresponds to HAL_SECRET_KEY environment variables. |
| list-secretsA | Get a list of available secret keys that can be used with {secrets.key} syntax. Only shows the key names, never the actual secret values. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api-docs | Documentation for available HTTP API tools |
TDQS
Scored across 8 tools
Each tool corresponds to a distinct HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS) plus a separate secrets management tool. There is no overlap in purpose.
All HTTP tools use a consistent 'http-<method>' naming pattern, and 'list-secrets' follows a similar verb-noun pattern. The naming is predictable and uniform.
With 8 tools covering standard HTTP methods and secrets management, the count is well-scoped for an HTTP API layer. No tool feels extraneous or missing.
The set includes all common HTTP methods (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS) along with secrets management, providing full coverage for typical HTTP interactions.