Skip to main content
Glama

goreminders_guide

Provides step-by-step guidance for navigating GoReminders: sign in, review appointments and customer replies, and manage reminder workflows. Use it first to find the right screens for your task.

Instructions

How to work in GoReminders (review appointments, customer replies and reminder workflows): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in GoReminders, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it discloses the topical content (screens, sign-in link) but never states the return form, whether it performs any action, or whether the call is side-effect free. For a guide/orientation tool the risk is low, so a 3 is fair, but nothing here reassures the agent about behavior beyond subject matter.

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 short sentences, nothing redundant, with the content scope up front and the call-order instruction at the end. The punctuation is slightly awkward but there is no wasted wording to cut.

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 zero-required-parameter orientation tool with no annotations and no output schema, the description should convey what the caller gets back (text instructions, a URL, screen map). It implies content via 'its screens and the sign-in link' but leaves the return shape and depth unstated, so it is adequate rather than complete.

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?

There is one optional parameter and schema coverage is 100%, so the schema already documents 'task'. The description adds only indirect signal — that tasks fall into reviewing appointments, customer replies, and reminder workflows — without explaining how free-text task phrasing affects the response. Baseline 3 applies.

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 recognizable resource — a guide to 'how to work in GoReminders' — and scopes it to screens, sign-in link, and the domains of appointments, replies, and reminder workflows. The verb is soft ('how to work in') but an agent can tell this is the orientation/doc tool rather than one of the click/type/read UI primitives named in the sibling list.

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

Usage Guidelines4/5

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

The closing directive 'Call this first' gives explicit ordering guidance relative to the other GoReminders tools, which is the key usage decision here. It does not say when to skip it or which sibling to use instead, so it stops short of full when/when-not coverage.

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