Skip to main content
Glama

whats_new

Retrieve AI news items published in the last seven days since the last checkpoint, organized by category, to answer "what's new" requests; the call marks them as seen.

Instructions

What's New: Items collected since the last Checkpoint and published in the last 7 days.

    Use only when the user asks for what is new since they last looked: what's new in
    AI or in some Categories, anything new, today's briefing. Calling it marks Items as
    seen and cannot be undone, so for anything else use `search`, which never does: a
    time span ("today", "recently", "this week"), a subject ("what's new with MCP"), or
    when unsure. Each Category has its own Checkpoint;
    only the Checkpoints of the Categories asked about (omitted: all) move to now, so
    Items shown once are not shown again. Every client of this server shares the
    Checkpoints. `previous_checkpoints` gives each asked Category's Checkpoint before this
    call (null: never viewed). If `items` is empty, tell the user when they last looked
    and offer `search` for recently published Items.

    Results are newest first, up to `limit` (default 100); Items published at the same
    time are never split, so a few more or fewer can be shown. `more` counts the Items
    left out; they count as seen too, so tell the user and offer `search` with the same
    `categories`, `since` 7 days ago and `until` the oldest shown Item's `published_at`.
    Summaries are plain text cut to about 500 characters; `read_item` gives the full text.

    Categories (an Item can be in several):
    News: Events in the AI industry, such as launches, funding, policy, and people
    changes.
    Applications: New AI products or tools that you can use right away.
    Engineering: Content about how to build AI systems, such as technical posts,
    frameworks, lessons from practice, and releases.
    Models: Newly released or newly listed AI models, and changes to what they can do and
    what they cost. Academic papers and theory are not included.

    If the data is over 24 hours old this collects first, which can take about a minute;
    `note` says when the collection was still running. `warning` names Sources that
    failed 3 or more collections in a row: tell the user.
    

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": "whats_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoriesNo

Output Schema

NameRequiredDescriptionDefault
moreNo
noteNo
itemsYes
warningNo
previous_checkpointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description explains the actual mutation: calling it advances per-Category Checkpoints, cannot be undone, and is shared across all clients of the server. It also discloses collection latency (~1 minute when data is over 24 hours old), the `note` and `warning` fields, and that overflow Items count as seen — all behavior beyond what annotations convey.

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?

Front-loaded with purpose and the destructive side effect before the alternatives, then organized into results, categories, and freshness paragraphs. Dense but nearly every sentence carries operational information; the Category glossary is long but necessary given 0% schema coverage.

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

Completeness5/5

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

Despite an output schema existing, the description still explains the non-obvious return fields (`previous_checkpoints`, `more`, `note`, `warning`) and prescribes follow-up actions for empty results and overflow. Nothing an agent needs to call this correctly or interpret its response is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load, and it does: `categories` omitted means all Categories and only the asked Categories' Checkpoints move; `limit` defaults to 100 and same-timestamp Items are never split, so counts can vary slightly. It also defines the four Category enum values with concrete scope, including what Models excludes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Items collected since the last Checkpoint and published in the last 7 days') and immediately distinguishes itself from the sibling `search` by its side effect. An agent can tell exactly what this returns without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use triggers ('what's new in AI', 'anything new', 'today's briefing') and explicit when-not cases (a time span, a subject, or when unsure) with the named alternative `search` and the reason it is preferred. This is the strongest form of routing guidance.

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

Deploy Server

Other Tools