nofax
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nofax_notifyA | Send a one-way phone notification. This tool is informational and does not create a human-response wait. Notification transport success never counts as approval. |
| nofax_request_approvalA | Send Allow/Deny to the phone and return a durable pending requestId. IMPORTANT: after this tool returns pending, call nofax_wait_for_response and repeat while it remains pending. Never continue the guarded action without a terminal Allow response. Set allowRefine when the human should also be able to send refinement text. |
| nofax_request_choiceA | Send up to three explicit options to the phone and return a durable pending requestId. IMPORTANT: call nofax_wait_for_response and repeat while pending; do not choose on the human's behalf. |
| nofax_request_refinementA | Ask the human for free-text refinement through the configured Nofax Refine iOS Shortcut. Use this when free-text edits are needed; use nofax_request_approval for Allow/Deny or nofax_request_choice for predefined options. Returns a durable pending requestId; call nofax_wait_for_response and repeat while pending. |
| nofax_wait_for_responseA | Long-poll a durable Nofax request for up to 240 seconds. If the result is pending, you MUST call this tool again with the same requestId. Repeat indefinitely until a terminal response is returned or the user explicitly changes/cancels the goal. Do not continue the guarded action while pending. |
| nofax_get_requestA | Inspect safe metadata and terminal state for one known durable requestId without waiting. Use nofax_wait_for_response when the caller must wait for a human decision, or nofax_list_pending to recover requestIds after interruption. Secret response topics are never returned. |
| nofax_list_pendingA | List a bounded set of unresolved Nofax request handles for recovery after client or conversation interruption. Secret response topics are never returned. |
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 7 tools
The three request tools are clearly differentiated by response type (choice, refinement, approval), and wait/get/list separate polling, inspection, and recovery. Minor overlap exists between get_request and wait_for_response, but the descriptions explicitly state when each is appropriate.
All tools share the nofax_ snake_case prefix and mostly follow a nofax_<verb>_<object> pattern. The request_* group is consistent, but list_pending is vaguer than list_pending_requests, and wait_for_response versus get_request mixes slightly different verb styles.
Seven tools fit the narrow human-approval domain well, covering request creation variants, polling, inspection, pending recovery, and one-way notification. There is no redundancy or excessive granularity.
The set covers creation of three request types, long-poll waiting, non-blocking status inspection, pending recovery, and one-way notification. A slight gap is the lack of an explicit cancel or expire tool for pending requests, but the core human-in-the-loop workflow is otherwise well covered.