Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BLIPR_URLNoBase URL of your Blipr server (hosted or self-hosted).https://blipr.dev
BLIPR_TOPICNoDefault topic used when a tool call omits one.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_alertA

Send a push notification to the user's phone via Blipr. Use this to reach the human: a long task finished, a build broke, you need approval, or you're blocked and need input. Priority 1 (silent) to 5 (critical); defaults to 3.

send_criticalA

Send a priority-5 critical page. Use ONLY for things that genuinely cannot wait (production down, urgent approval, safety). Bypasses silent/Focus when the Blipr app has Apple's Critical Alerts entitlement enabled; otherwise it is delivered as time-sensitive.

askA

Send a yes/no question (or, with options, a multiple-choice question) to the user's phone via Blipr and BLOCK until they tap an answer, then return it. This is a human-in-the-loop approval gate: use it before doing something consequential or irreversible (deleting prod data, force-pushing, spending money, sending an email) — anything where you'd otherwise ask 'should I proceed?'. The call does not return until the human answers or it times out. Returns { responded, approved, value, message_id, topic } — ALWAYS branch on approved: it is true ONLY when the human tapped Yes, and false on No, a timeout, or an error. Never treat a non-approval as a go-ahead. With options, the result has no approved: value is the option the human tapped, exactly as you passed it (trimmed). On timeout (or if your client cancels the call) the human may still answer within ~30 min — call check_reply with the returned message_id to resume rather than re-asking.

request_ackA

Send a message that needs the human to acknowledge it, and BLOCK until they tap 'Acknowledge', then return. Use this when the human must see and confirm receipt of something before you continue (a heads-up they have to read, a checkpoint reached, 'I'm about to start the long run'). The call does not return until the human acks or it times out. Returns { responded, message_id, topic } plus replied_at when acked (responded:true), or { responded: false, reason: "timeout" } if no one acks in time. On timeout/cancel, call check_reply with the returned message_id (replies are retained ~30 min).

check_replyA

Look up whether the human has replied to a question or ack you sent earlier — use it to resume after ask/request_ack returned a timeout, or after your client cancelled the blocking call. Pass the message_id (and topic) you got back from that call. Returns immediately by default; set wait_seconds to briefly long-poll. Returns { responded, value?, replied_at? } — value is "yes"/"no" (a yes/no question), the chosen option (a multiple-choice question) or "ack". For an approval gate, only proceed when value === "yes". Replies are kept only ~30 minutes after the original message was sent.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation4/5

Each tool maps to a distinct interaction mode: blocking question (ask), blocking acknowledgement (request_ack), non-blocking notification (send_alert), escalation (send_critical), and async polling (check_reply). The one soft overlap is send_alert vs send_critical, since send_alert at priority 5 does nearly the same job as send_critical; ask vs request_ack is clarified by their descriptions but still requires reading to distinguish.

Naming Consistency4/5

All names are lowercase snake_case and four of five follow a verb_noun shape (check_reply, request_ack, send_alert, send_critical). The bare verb `ask` is the only deviation, and it is short and unambiguous rather than genuinely inconsistent.

Tool Count5/5

Five tools is tightly scoped for a human-in-the-loop notification/approval service, and each one covers a genuinely different interaction pattern (ask, ack, notify, escalate, resume). Nothing looks like a redundant wrapper or a filler tool.

Completeness4/5

The core lifecycle — send notification, page critically, ask a question, request an ack, and resume a timed-out call — is fully covered. Minor gaps remain: no non-blocking question send (all questions block), no message listing/cancel/history, and send_alert's description doesn't state that it returns a message_id, which would make follow-up polling awkward.

Maintenance

ActivityActive
ResponsivenessLimited data