Skip to main content
Glama

goreminders_read

Read the current GoReminders page to extract visible text plus numbered buttons, links, and fields, with optional scope to a single element for focused inspection.

Instructions

Read the current GoReminders page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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. 'Read' conveys non-mutation and the enumeration of returned content (text, numbered buttons, links, fields) is genuine behavioral detail, but it says nothing about whether the call is a snapshot, whether it waits, or what happens if no page is open.

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?

One front-loaded sentence with no filler; the key resource and payload are named up front. The clipped list style is efficient, though it ends up leaving behavioral gaps that brevity alone shouldn't excuse.

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 one-parameter, read-only tool with no output schema, the description covers roughly the right surface and usefully explains that buttons are numbered (which pairs with goreminders_click). It still leaves out preconditions and the scope semantics of the `element` parameter, which an agent needs before relying on it.

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?

The single optional `element` parameter is already fully documented in the schema (100% coverage), so the baseline applies. The description mentions reading 'inside an element' only implicitly through the word 'current' and adds no scoping or syntax meaning beyond the schema.

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 (Read) and resource (the current GoReminders page), and enumerates what comes back: text, numbered buttons, links and fields. That is concrete enough to distinguish it from the action siblings (click, type, open, close), though it doesn't explicitly contrast with goreminders_status.

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 when-to-use or when-not-to-use guidance and no prerequisites. The word 'current' hints that a page must already be open via goreminders_open, but nothing states that dependency or tells the agent when to read versus call goreminders_status.

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