Skip to main content
Glama
AarsyDesign

PushNotif MCP Server

by AarsyDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_app

Register an additional website or mobile app in your PushNotif workspace and generate its unique ECDSA P-256 VAPID keypair. Use for new domains or apps, not branding updates.

Instructions

Register an additional website or mobile application under the authenticated PushNotif workspace and generate its unique ECDSA P-256 VAPID keypair. Use this tool when an authenticated user wants to add a new website domain or app; do not use it to modify an existing app's logo or welcome message (use update_app_branding instead) or to register a brand-new user account (use register_new_account instead). Requires PUSHNOTIF_API_KEY, costs 0 credits, and creates a persistent app record. Returns JSON { ok, app: { id, site_name, site_url, vapid_public_key, created_at }, sdk_snippet }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYesCanonical HTTPS URL of the website (must start with https:// or http://localhost)
site_nameYesDisplay name of the website or mobile application (2 to 80 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.2
    • changedInput schema / properties / site_name / description
      Previous value: -"Nama website atau aplikasi"New value: +"Display name of the website or mobile application (2 to 80 characters)"
    • changedInput schema / properties / site_url / description
      Previous value: -"URL domain lengkap dengan https://"New value: +"Canonical HTTPS URL of the website (must start with https:// or http://localhost)"
  2. First observedv2.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the required credential PUSHNOTIF_API_KEY, the cost (0 credits), and that a persistent record is created. Those are operationally significant facts an agent cannot derive from the annotation block.

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

Conciseness4/5

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

Three sentences, front-loaded with purpose, then routing, then operational facts; every sentence carries information. It is dense and slightly long, but with no output schema present the inline return-shape sentence earns its place.

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?

For a write tool with no output schema the description covers auth requirements, cost, persistence semantics, routing alternatives, and the returned JSON payload shape. An agent has everything needed to call it correctly and know the outcome.

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?

Schema description coverage is 100%, so site_url's HTTPS/localhost constraint and site_name's 2-80 character range are already fully documented in the schema. The description adds no additional parameter-level syntax or format detail, so the baseline of 3 applies.

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?

States a specific verb (register/create) plus the resource (website or mobile app under the PushNotif workspace) and the side effect (generating an ECDSA P-256 VAPID keypair). It explicitly distinguishes itself from update_app_branding and register_new_account, so an agent can select it without opening sibling schemas.

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?

Gives an explicit when-to-use condition ('authenticated user wants to add a new website domain or app') plus two explicit when-not-to-use cases, each naming the correct alternative tool. Nothing about routing is left to inference.

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