Skip to main content
Glama

RenewRoster

Get reminder schedule

get_reminders
Read-onlyIdempotent

Days before expiry when reminders go out, for domains and SSL.

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": "get_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful scope by saying the result concerns domains and SSL and explains that the values are days before expiry, but it does not describe return shape or whether the schedule is global versus per-asset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence fragment with no wasted wording, and the domain/SSL scope is placed at the end rather than buried. It could be slightly stronger with a clear verb at the front, but it is appropriately sized for a zero-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter read tool with annotations covering safety, the description gives enough to understand that the tool returns reminder lead times for domains and SSL. However, because there is no output schema, it should more clearly state what the response looks like or whether the reminders are a schedule object rather than a list.

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?

There are zero parameters, so there is no parameter semantics burden for the description. The baseline score of 4 applies because the schema is empty and the description does not need to compensate for undocumented inputs.

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?

The description identifies the resource as the reminder schedule and scopes it to domains and SSL, which is specific enough to distinguish it from unrelated siblings like get_asset or lookup_domain. It lacks an explicit verb such as 'returns' or 'retrieves', but the title 'Get reminder schedule' and the reminder-specific wording make the purpose clear.

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?

The description only states what the reminder schedule covers and gives no guidance on when an agent should call this tool instead of alternatives such as list_expiring or lookup_domain. There are no exclusions, prerequisites, or contextual cues beyond the domain/SSL scope.

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.