Skip to main content
Glama

RenewRoster

List expiring domains and certificates

list_expiring
Read-onlyIdempotent

Domains and SSL certificates expiring within N days (default 30), soonest first. Includes already expired ones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_expiring"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses useful behavior: results are ordered soonest-first and already-expired entries are included. It omits auth requirements, paging, and result shape, but the added behavioral context is meaningful.

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 tightly written sentences, zero filler, with the resource scope front-loaded ahead of the ordering and inclusion caveats.

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?

With no output schema, an agent still knows what the tool returns at a conceptual level (domains and certs, sorted, including expired). Gaps remain around whether both types are returned when 'type' is omitted and whether results are paged, but nothing critical is missing for a simple read tool whose safety profile is already annotated.

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 coverage is 0%, so the description must supply parameter meaning. It does explain the key semantic of 'days' (expiry window with a default of 30, which the schema itself does not declare), but the 'type' parameter is only implied by 'Domains and SSL certificates' – it never says whether omitting it returns both kinds or how the enum maps to the results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the exact resource set (domains and SSL certificates), the filter condition (expiring within N days), and the sort order, so intent is unambiguous. It doesn't name sibling tools like lookup_domain or lookup_cert to sharpen the distinction, keeping it from a 5.

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

Usage Guidelines3/5

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

The only usage signal is the implied 'check what's expiring soon' scenario plus the '(default 30)' default. There's no explicit when-to-use guidance, no note on when to prefer lookup_domain/lookup_cert, and no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.