Skip to main content
Glama

goreminders_status

Check your Cotlet.dev account, available credits, and GoReminders connection status to confirm everything is ready before using reminder features.

Instructions

Check that your Cotlet.dev account and GoReminders are ready: account, credits and GoReminders connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short: it doesn't say this is read-only and side-effect free, doesn't indicate whether it makes network calls to GoReminders, and doesn't describe what a failed or partially-ready state looks like.

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?

A single front-loaded sentence with no filler. Minor redundancy between "your Cotlet.dev account" and the trailing "account," but nothing that wastes meaningful space.

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?

There is no output schema, so the description should at least sketch what the status result reports (per-check pass/fail, credit balances, connection state) and what an agent should do with a negative result. For a simple zero-arg diagnostic it is adequate, but an agent cannot predict the response shape.

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 zero parameters, so the baseline is 4; there is no parameter semantics to compensate for and nothing is left ambiguous about the call signature.

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 a specific verb ("Check") and enumerates the resources verified: account, credits, and the GoReminders connection. It does not differentiate from the sibling action tools (open/click/type/read/close), but the readiness-check framing is clear enough to distinguish it by intent.

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 guidance on when to run this versus the sibling tools, no prerequisites, and no statement of whether it should be called before the open/click/type tools to validate the setup. The purpose implies a pre-flight check but the description never says so.

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