Skip to main content
Glama
applogico

blipr-mcp

by applogico
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Page the user (critical)

send_critical

Send a priority-5 critical push alert for production outages, urgent approvals, or safety issues; bypasses silent/Focus when Critical Alerts are enabled.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
titleNoShort title.
topicNoTopic to publish to. Pass it explicitly — each project should use its own topic. When omitted, falls back to the project's `.blipr-topic` file, then the BLIPR_TOPIC env var.
messageYesWhat is wrong or what you need, urgently.
markdownNoRender the body as Markdown (bold, italics, links, code). Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.3
    • addedInput schema / properties / markdown
      Added value: +{
+  "description": "Render the body as Markdown (bold, italics, links, code). Off by default.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / topic / description
      Previous value: -"Topic. Defaults to BLIPR_TOPIC."New value: +"Topic to publish to. Pass it explicitly — each project should use its own topic. When omitted, falls back to the project's `.blipr-topic` file, then the BLIPR_TOPIC env var."
  3. First observedv0.3.1

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Since there are no annotations, the description must carry the burden. It adds crucial behavioral context by explaining the delivery mechanism, specifically that it 'Bypasses silent/Focus' modes under certain entitlements, which is vital for an AI understanding the impact of this call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and highly front-loaded, defining the urgency immediately. It is concise and highly efficient, providing necessary technical details without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high severity and technical complexity of a critical paging tool, the description provides all necessary context regarding use cases and delivery behavior. Nothing critical is missing from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, meaning the structured fields already define the parameters adequately. The description provides the necessary *context* for the call but adds little semantic value beyond the overall urgency.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The purpose is crystal clear: 'Send a priority-5 critical page.' It strongly implies its difference from a standard 'alert' by defining it as a high-priority, necessary, and time-critical communication channel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides extremely strict usage guidelines, advising the agent to use the tool 'ONLY' for genuinely critical scenarios like production downtime, urgent approval, or safety issues. This effectively tells the AI when *not* to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools