Skip to main content
Glama

Daily Tonic by Coach Moshiur

Recent Daily Tonics

get_recent_tonics
Read-only

The titles, tiny steps and links of the Daily Tonics of the last days (newest 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": "get_recent_tonics"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back. Default 7.
readerNoWho the tonic is written for. Default all (everyone).
languageNoLanguage: en English, bn Bangla, ar Arabic, ur Urdu, zh Chinese. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, establishing a safe closed-world read, so the bar is lower. The description adds genuine value by disclosing the returned fields (titles, tiny steps, links) and newest-first ordering, but says nothing about result volume, what happens when no tonics exist, or whether today is included.

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, and the ordering note is placed where it is immediately useful. It is efficient, though the compressed phrasing ("the last days") leaves the range bound for the agent to discover in the schema.

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

Completeness4/5

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

With no output schema, the description correctly takes on the job of enumerating returned fields and ordering, and the three optional parameters are fully documented in the schema. Only edge-case behavior (empty results, whether the current day is included) is left unstated, which is minor for a simple read.

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?

Schema description coverage is 100%, including defaults and enum meanings for reader and language, so the schema carries the parameter burden. The description only echoes the days concept via "last days" and adds no syntax, format, or interaction detail 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?

"The titles, tiny steps and links of the Daily Tonics of the last days (newest first)" names the resource, the returned fields, and the ordering in one clause. The contrast with get_todays_tonic is implicit in "last days" rather than stated, so it stops just short of explicit sibling differentiation.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase "of the last days" suggests a multi-day retrospective as opposed to a single-day lookup, which the agent can loosely map onto get_todays_tonic. There is no explicit when-to-use, when-not-to-use, or named alternative.

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.

Resources