Skip to main content
Glama

ReminderIt

by com.reminderit
OverviewDiscussionsAdmin

Get account details

whoami
Read-onlyIdempotent

Identify the connected ReminderIt account: who it is, their timezone, plan and quota.

Two jobs. First, it is the connection check — call it when the user asks "am I
connected?", "which account is this?", or when another tool returns an auth error,
to confirm the API key is valid and see whose account it opens.

Second, call it BEFORE creating or rescheduling a reminder: it returns the user's
saved timezone, so you can schedule silently instead of asking. It also warns when
the phone is unverified or the account is opted out — in either case no reminder can
be delivered, so surface that before scheduling anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context — that it can reveal delivery blockers (unverified phone, opted-out account) and that these block reminder delivery, which is not encoded anywhere in the structured fields.

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?

Front-loaded with the core identity statement, then split into two clearly labelled jobs. Every sentence carries actionable information; nothing is repeated from the title or annotations.

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?

An output schema exists, so return-value explanation is unnecessary, and the description instead supplies the pre-call reasoning (auth validation, timezone reuse, delivery blockers) an agent needs to use the tool correctly.

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?

The tool takes no parameters, so per the baseline no compensating parameter documentation is needed and the schema (empty object) is fully aligned with the description.

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 and resource ('Identify the connected ReminderIt account') and enumerates the returned dimensions (identity, timezone, plan, quota). It is clearly distinguishable from get_usage or get_voice_settings by scoping to account identity.

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 names two triggering conditions: connection/auth-error checks, and calling BEFORE creating or rescheduling a reminder to reuse the saved timezone. It goes further by stating when not to proceed (unverified phone or opted-out account) rather than leaving that to inference.

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

All ReminderIt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources