A
licenseA
qualityC
maintenanceLets you send push notifications to your phone via ntfy, enabling alerts from scheduled tasks or direct messages.
Last updated
2
MIT
selfping
by com.selfping
Server Details
Text your own phone when a run finishes or needs you. A key can only message its own number.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.8/5.0
Tool DescriptionsA
Average 4.7/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly defined and distinct.
Naming Consistency5/5
The tool name 'send_ping' follows a clear verb_noun pattern. With a single tool, naming is inherently consistent and predictable.
Tool Count5/5
One tool is exactly appropriate for a service that performs a single, focused action. The server's purpose is narrow, so the tool count matches the scope perfectly.
Completeness5/5
The tool fully covers the server's stated purpose of notifying the operator. No additional operations are needed for this domain, so the surface is complete.
Available Tools
1 toolsend_pingSend myself a textAInspect
Send a text message to the phone number that owns this SelfPing API key. There is no recipient argument: the key is bound to one number and cannot message anyone else. Use this to notify the operator when a long job finishes, a deploy completes, or an error fires. Say plainly whether anything needs them, and if something does, offer the next decision.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | The text to deliver. Keep it under 160 characters. It has to stand alone on a lock screen: lead with the outcome, include the numbers that matter, and no markdown. |
Tool Definition Quality
A4.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=false and openWorldHint=true, but the description adds crucial behavioral context: the key is bound to one number and cannot message anyone else. This constraint is not visible in the schema or annotations and meaningfully affects usage, so the description earns credit beyond annotations.
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 three sentences long, front-loads the core purpose, then adds a constraint and usage examples. Every sentence earns its place with no fluff or repetition of the title or schema.
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?
With a single parameter, full schema coverage, and no output schema, the description provides complete context: what it does, who receives it, when to use it, and how to phrase the message. No gaps remain for the agent to guess.
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?
Input schema covers 100% of parameters and the 'message' parameter already has rich description. The tool description adds extra guidance on message composition ('Say plainly whether anything needs them, and if something does, offer the next decision'), which goes beyond the schema's lock-screen advice. This pushes the score above the baseline of 3.
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 uses a specific verb-resource pair ('Send a text message to the phone number that owns this SelfPing API key') and clearly distinguishes itself by explicitly stating there is no recipient argument. This makes the tool's purpose unambiguous and well-scoped.
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 explicit 'when to use' guidance: 'Use this to notify the operator when a long job finishes, a deploy completes, or an error fires.' It also gives style guidance for the message ('Say plainly whether anything needs them...'), which is valuable for correct invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceEnables sending SMS text messages through Twilio's messaging service with a simple send_text tool that supports configurable recipients and messaging service integration.Last updated169MIT
- AlicenseAqualityCmaintenanceEnables sending iMessages or SMS messages via the macOS Messages app using osascript. No Full Disk Access required, and never reads your message history.Last updated1MIT
- Flicense-qualityDmaintenanceEnables AI agents to send SMS/iMessage and check replies via Sendblue API using secure polling (no webhooks).Last updated4