Utility Matrix

Certificate Expiry Checker

certificate-expiry-checker

Read-onlyIdempotent

Assess certificate expiry risk given a domain and days remaining. Returns risk level (OK, WARNING at <30 days, CRITICAL at <7 days, EXPIRED at <0).

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name (e.g. "api.example.com")
`days_remaining`	Yes	Days until certificate expires

Output Schema

Name	Required	Description	Default
`domain`	Yes
`next_step`	Yes
`risk_level`	Yes
`next_step_url`	Yes
`why_follow_up`	Yes
`days_remaining`	Yes
`interpretation`	Yes
`affiliate_context`	No
`computation_basis`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026
- addedInput schema / properties / domain / maxLength
```
Added value: +253
```
Changed2 schema fields changedSep 28, 2026
- addedInput schema / properties / days_remaining / examples
```
Added value: +[
+  1
+]
```
- addedInput schema / properties / domain / examples
```
Added value: +[
+  "example.com"
+]
```

Changed1 schema field changedJul 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "affiliate_context": {
+      "additionalProperties": false,
+      "properties": {
+        "affiliate": {
+          "type": "string"
+        },
+        "cta_label": {
+          "type": "string"
+        },
+        "disclosure": {
+          "type": "string"
+        },
+        "framing": {
+          "type": "string"
+        },
+        "posture": {
+          "enum": [
+            "secondary"
+          ],
+          "type": "string"
+        },
+        "slot_id": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        },
+        "variant": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "affiliate",
+        "cta_label",
+        "disclosure",
+        "framing",
+        "posture",
+        "slot_id",
+        "url",
+        "variant"
+      ],
+      "type": "object"
+    },
+    "computation_basis": {
+      "type": "string"
+    },
+    "days_remaining": {
+      "type": "number"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "risk_level": {
+      "type": "string"
+    },
+    "why_follow_up": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "computation_basis",
+    "days_remaining",
+    "domain",
+    "interpretation",
+    "next_step",
+    "next_step_url",
+    "risk_level",
+    "why_follow_up"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 13, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJun 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, openWorld=false, destructive=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the exact risk-tiering thresholds (WARNING <30 days, CRITICAL <7, EXPIRED <0), which tell the agent how the tool reasons about its input.

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, no filler, with the purpose front-loaded and the return semantics second. Every clause carries information an agent can act on.

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?

A pure two-parameter computation with full schema coverage, safety annotations, and an output schema, so return format needn't be explained. It is essentially complete, with only the missing usage context as a minor gap.

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 description coverage is 100%, so the baseline is 3. The description goes further by tying meaning to the days_remaining value through the threshold bands, letting an agent anticipate the outcome for a given input rather than just pass a number through.

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?

States a specific verb ('Assess') and resource ('certificate expiry risk') plus the exact inputs it consumes ('domain and days remaining'). It is immediately distinguishable from siblings like known-vulnerability-checker or dockerfile-linter without opening any schema.

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

Usage Guidelines2/5

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

No when-to-use guidance, no mention of when this is NOT appropriate, and no alternatives named among the large sibling set of calculators. The only hint is the input phrasing 'given a domain and days remaining', which specifies inputs rather than usage context.

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

All Utility Matrix tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?