Skip to main content
Glama

Daily Tonic by Coach Moshiur

Today's Daily Tonic

get_todays_tonic
Read-only

Today's Daily Tonic by Coach Moshiur: a short leadership and personal-growth thought, one tiny step to take today, and a question to reflect on, with a link to read it on the web.

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

Input Schema

NameRequiredDescriptionDefault
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

B3.2/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, so the safety profile is covered. The description adds real value by disclosing the return contents (thought, step, question, link) in the absence of an output schema, but says nothing about failure modes or whether content is cached/generated live.

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 compact sentence that front-loads the resource and then enumerates the payload. It mildly restates the title but every remaining clause earns its place by describing return contents.

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?

For a simple, zero-required-parameter read-only fetch with fully documented enums, the description covers what the agent needs to call it and what comes back. Only the absence-vs-archive behavior is left unstated, which is a minor gap rather than a blocker.

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% with both enums fully documented, including defaults, so the schema carries the parameter burden. The description mentions the tonic's targeting not at all, adding no meaning beyond what the schema already provides; 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?

The description names the resource (Today's Daily Tonic) and spells out its contents precisely: a leadership/personal-growth thought, a tiny step, a reflection question, and a web link. It lacks any differentiation from the sibling get_recent_tonics, so an agent must infer that this returns only today's edition.

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?

Beyond the word "Today's" implying a current-day fetch, there is no when-to-use guidance, no mention of the archive sibling get_recent_tonics, and no statement about what happens if no tonic exists for today. Usage is left entirely to inference from the name.

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