Skip to main content
Glama
pasihaka

MCP Sentinel

by pasihaka
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

get_monitor_badge

Read-only

Generate dynamic SVG status badges and Markdown snippets to display real-time uptime, protocol version, and operational status of monitored MCP servers in READMEs or status pages.

Instructions

Generates dynamic SVG status badge links and Markdown embed snippets for an MCP Sentinel uptime monitor. Use this tool when you want to display the real-time operational status, protocol version, and uptime badge of a monitored MCP server directly inside a GitHub repository README, developer documentation, or status page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monitorIdYesThe unique identifier of the monitor (or "sample" / "demo" to preview a demonstration badge).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesGenerated SVG badge URLs and copy-paste markdown embed snippet.
isErrorYesWhether an error occurred while generating badge snippets.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / monitorId / description
      Previous value: -"The monitor ID or identifier"New value: +"The unique identifier of the monitor (or \"sample\" / \"demo\" to preview a demonstration badge)."
    • addedInput schema / properties / monitorId / examples
      Added value: +[
+  "demo",
+  "mon_prod_01",
+  "sample"
+]
    • addedInput schema / properties / monitorId / minLength
      Added value: +1
    • addedOutput schema / additionalProperties
      Added value: +false
    • addedOutput schema / properties / content / description
      Added value: +"Generated SVG badge URLs and copy-paste markdown embed snippet."
    • changedOutput schema / properties / content / items / properties / text / description
      Previous value: -"Badge URLs and markdown snippets"New value: +"Badge URL and Markdown snippet."
    • changedOutput schema / properties / content / items / properties / type / description
      Previous value: -"Content MIME type"New value: +"Content MIME type."
    • changedOutput schema / properties / isError / description
      Previous value: -"Whether an error occurred"New value: +"Whether an error occurred while generating badge snippets."
    • changedOutput schema / required
      Previous value: -[
-  "content"
-]New value: +[
+  "content",
+  "isError"
+]
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds complementary behavioral context: the tool emits embeddable snippets and links reflecting real-time monitor status rather than mutating anything. No contradiction with annotations; the generate-and-return behavior is fully consistent with a read-only hint.

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 the core function, followed by concrete usage context. No filler words; each sentence earns its place.

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 tool is simple (one parameter, no nested objects), has a full input schema, a read-only annotation, and an output schema. The description covers purpose, output artifact type, displayed content, and target destinations. Nothing essential for an agent to invoke it correctly is missing; the output schema handles return-value details.

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%, with the monitorId parameter fully documented including examples ('demo', 'mon_prod_01', 'sample') and an explanation of preview values. The tool description adds no parameter-level details beyond the schema, so the baseline of 3 is appropriate.

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 names a specific verb ('Generates'), a concrete artifact ('dynamic SVG status badge links and Markdown embed snippets'), and a clear domain ('MCP Sentinel uptime monitor'). The contents of the badge (real-time operational status, protocol version, uptime) are explicit. The sibling tools (audit_mcp_server, verify_mcp_protocol) perform clearly different actions, so no confusion is possible.

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 second sentence gives an explicit trigger condition: 'Use this tool when you want to display...' with concrete destinations (GitHub README, developer documentation, status page). It does not name alternatives or state when not to use the tool, but the usage context is specific enough for an agent to route correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pasihaka/mcp-sentinel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server