Skip to main content
Glama
Sign In
Prufa

Prufa

Official
by prufa-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

prufa_set_notifications

Configure the notification routing matrix for 9 events, mapping each to email and Slack channels with boolean values. Returns locked events that cannot be disabled.

Instructions

Set the notification routing matrix: 'cells' is the 9-event x {email, slack} map of booleans deciding which channel each event fires on. The server validates keys and types (422 on unknown/missing keys or non-booleans) and returns {cells, locked_events} (events you can't turn off). [Pro]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cells": "<cells>"
    },
    "name": "prufa_set_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
cellsYes9-event x {email, slack} routing matrix of booleans.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description describes validation behavior (422 errors) and response structure (cells and locked_events). It also indicates a Pro limitation. However, it does not disclose destructive nature or auth requirements.

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?

Two sentences, front-loaded with action, no redundant information. Every sentence provides essential detail about the tool's operation.

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

Completeness4/5

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

The description covers return values and validation, but lacks information about permissions and side effects. Given no output schema, it provides adequate context for a setter tool.

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

Parameters4/5

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

The schema has 100% coverage and the description adds value by explaining validation of keys and types, and the locked_events concept. This adds context beyond the schema's description of the parameter.

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 description clearly states the tool sets the notification routing matrix, a specific verb-resource combination. It distinguishes from sibling tools by focusing on notification routing, which is unique among the listed tools.

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

Usage Guidelines4/5

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

The description provides context on when to use the tool (to set routing), but does not explicitly exclude alternative tools. It mentions validation and response behavior, which guides usage implicitly.

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