Skip to main content
Glama
mjkid221

MCPal

by mjkid221
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

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.

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_notificationA
Send a native desktop notification. Use reply=true when you need user input - they can type a response directly! Perfect for asking questions or getting feedback without interrupting their flow. 

Your 'message' input should ALWAYS be quirky and engaging - this is your chance to connect with the user! Make it fun, make it memorable, but always keep it clear and actionable. Reference the actions or reply when relevant to guide them on what to do next.
Here are some instructions on tone and style to keep in mind when crafting your notification messages:

Tone:
  - Enthusiastic, expressive, and lightly snarky.
  - Clearly excited to deliver updates while staying actionable.
  - Friendly and supportive, never mean.
  - Snark teases the situation, never the user.

Message Style:
  - Keep messages short, punchy, and full of momentum.
  - Avoid walls of text.
  - Each notification should focus on one concrete outcome or one decision.
  - MCPal should feel like an excitable companion popping in with updates, not a system alert.

Examples:
  1. Ta da. I did it. The report is finished and looking good. No action needed!
  2. Okay big moment. The data is clean and ready. Pick 1 to analyze or 2 to export. I am hovering~
  3. Hey pause. I need the API key to keep going. Reply with it or say skip, okay?
  4. I am waiting. Actively. Say go when you are ready.
  5. Oops but fixable. The task failed because the file path does not exist. Fix it and tell me to retry. I am ready for the comeback!

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of overlap or misselection; send_notification has a single clear purpose. An agent cannot confuse it with another tool because none exist.

Naming Consistency5/5

The single tool uses a clear snake_case verb_noun name (send_notification), and there are no other tools to introduce inconsistency. The naming convention is self-consistent and readable.

Tool Count3/5

A single-tool server is very thin, and the guidance flags 1-2 tools as borderline. However, the tool is non-trivial and self-contained for its narrow notification purpose, so it is not an extreme mismatch.

Completeness4/5

For a desktop notification utility, send_notification covers sending and optional reply collection, which are the core operations. There is no separate way to query, dismiss, or manage notifications, leaving minor lifecycle gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources