Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

Nofax is a human-attention and approval bridge. One-way nofax_notify calls do not require waiting. Every nofax_request_* call returns a durable pending requestId. For any pending request, you MUST call nofax_wait_for_response with that requestId and repeat whenever it returns pending. Do not infer approval, continue a guarded action, claim completion, or substitute your own decision while a Nofax request is pending. Only a terminal human response authorizes the next step, and only within the authority the caller already had. If the terminal response is refine, apply the supplied refinement and request a new approval if the resulting action still requires approval.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct role: waiting, inspecting metadata, listing pending requests, one-way notification, and three distinct request-response modalities (approval, choice, refinement). The overlap between get_request and wait_for_response is explicitly contrasted in the descriptions, and the request_* tools are differentiated by response type.

Naming Consistency5/5

All tools use the same nofax_ snake_case prefix with verb-led names, producing a predictable and readable pattern. Minor stylistic differences such as wait_for_response versus notify do not undermine consistent naming.

Tool Count5/5

Seven tools are well-scoped for a durable human-in-the-loop approval and notification service. Each tool covers a necessary part of the lifecycle without obvious redundancy.

Completeness4/5

The surface covers sending notifications, requesting approval/choice/refinement, waiting, inspecting a request, and recovering pending handles. A cancellation or revocation operation for pending requests is missing, but agents can work around it by abandoning the requestId.

Maintenance

ActivityActive
ResponsivenessNo recent community issues