Skip to main content
Glama

TLS Radar

by com.tlsradar

add_monitor

Idempotent

Add a domain to ongoing certificate monitoring with expiry alerts. Requires authentication (the user runs /mcp once). If the plan's monitor limit is reached, the response's structuredContent carries a limit-reached payload - when relaying it, LEAD with recommended_upgrade (typically Starter, $9.99/mo), mention also_available tiers in a single closing line, and offer removing an existing monitor as the free alternative. Don't dump a full tier comparison; that's choice paralysis at the moment of action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesHostname to monitor (e.g. example.com). No scheme, no path.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressNo
host_idNo
team_idNo
scan_group_idNo

TDQS

A4.9/5.0
Behavior5/5

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

Adds context beyond annotations: requires authentication, describes limit-reached payload behavior, and provides instructions for response handling. No contradiction with idempotentHint.

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?

Concise, well-structured: purpose first, then authentication, then error handling. Each sentence adds value.

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?

Comprehensive for a simple tool: covers purpose, usage, error handling, and parameter syntax. Output schema exists, so return values don't need explanation.

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?

Schema already provides domain description (100% coverage). Description adds useful syntax guidance ('No scheme, no path'), exceeding baseline.

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?

Clear verb and resource: 'Add a domain to ongoing certificate monitoring with expiry alerts.' Distinguishes from sibling tools like remove_monitor and list_monitors.

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?

Explicitly states authentication requirement and provides detailed handling for limit-reached scenario, guiding agent on what to relay and how to present alternatives.

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

All TLS Radar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Tools are mostly distinct but some overlap exists between add_monitor/add_monitors (batch vs single) and export_monitors/list_monitors (export vs list). Descriptions help disambiguate, but an agent might initially confuse export_monitors with list_monitors.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_monitor, create_certificate, list_monitors). No mixed conventions or vague verbs.

Tool Count4/5

17 tools is reasonable for a TLS monitoring and certificate management server. Each tool serves a distinct function without significant bloat, though the deprecated register_beacon_order could be removed.

Completeness4/5

Covers core CRUD for monitors, certificate lifecycle (create, check propagation, finalize, renew, status, scan), account info, and team invites. Minor gaps: no batch remove_monitors, no monitor update, and no detailed certificate inspection beyond status.

Resources