jp-caa-orders
by pipeworx-io
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIPEWORX_API_KEY | No | Optional API key for a free Pipeworx account, raising the anonymous cap of 50 calls a day to 200 a day. Get a key at https://pipeworx.io/signup and add it to the server entry's env. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there. | |
| NODE_USE_ENV_PROXY | No | Set to 1 so newer Node releases honour HTTPS_PROXY, since Node's built-in fetch does not read HTTPS_PROXY by default. Used when running behind an HTTPS proxy. | |
| PIPEWORX_META_TOOLS | No | Set to 1 to also list ask_pipeworx and the other gateway-wide tools. By default the npm stdio bridge lists only this pack's tools. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues