Skip to main content
Glama

Daily stories

get_daily_stories
Read-only

The stories of a day (new every day) for the learner's language pair, with level and title in both languages. Only stories with status 'finished' have sentences.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD; default today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description does add genuinely useful non-obvious context: content regenerates daily, and only stories with status 'finished' carry sentences. It stops short of describing ordering, empty-day behavior, or what a partially finished story returns.

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, both front-loaded with substance: the first defines the payload, the second flags the status-dependent caveat. Nothing is padded or redundant.

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 simple read with no output schema, the description covers the fields returned (title and level in both languages) and the status caveat. It omits what an empty or unfinished day looks like and whether results are ordered, which leaves a modest gap given there is no output schema to fill it.

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?

Schema coverage is 100% and the single optional 'date' parameter is already documented as YYYY-MM-DD with a default of today. The description reinforces the 'a day' scoping without contradicting the schema; the schema carries the burden, so the baseline 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 states a concrete retrieval verb-resource pairing: the stories for a given day in the learner's language pair, returned with level and title in both languages. That is specific enough to distinguish a daily-list from a single-story fetch, but it never explicitly contrasts itself with the sibling get_story, leaving that separation to inference.

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: '(new every day)' hints that the content refreshes daily and the schema default of 'today' suggests the normal call pattern. There is no explicit statement of when to prefer this over get_story or how to handle a date with no stories, so the agent must infer the routing.

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