Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
collect_nowA

Collect new Items from every Source now.

    Use only when the user asks to refresh or collect now: `whats_new` already
    collects by itself when the data is over 24 hours old. Takes about a minute.
    Reports how many Items each Source added (0 for a failed one), and which Sources
    failed and why.
    
list_sourcesA

Every Source with its URL, default Categories and collection state.

    The state is when it was last tried, when it last succeeded, its last error and
    how many collections in a row it has failed. The last error is kept after a success,
    so with 0 failures in a row it is from before `last_success_at`. Use it to check
    which Sources work.
    
searchA

Search stored Items by text, publish time, Category and Source, in any mix.

    Use for a question about a subject or time span, such as last week's Engineering
    Items about MCP or what was published today, and whenever `whats_new` is not
    clearly asked for. Every filter is optional; an omitted one matches every Item.
    `query`: the title or the whole summary contains it (case-insensitive).
    `since` / `until`:
    published at or after `since` and before `until`, ISO 8601; a time without an
    offset, or a date alone (midnight), is UTC. `categories`: in any of them (News,
    Applications, Engineering, Models; see `whats_new`). `sources`: from any of these
    Source ids (see `list_sources`). An empty `categories` or `sources` list matches
    nothing. Results are newest first, at most `limit` (default 20). A summary shown is
    plain text cut to `summary_length`, about 500 characters by default; a shorter
    length skims many Items by title, 0 shows none, and `read_item` gives the full text.
    Searching never moves a Checkpoint.
    
read_itemA

The full text of an Item: fetches its original page and extracts the main text.

    Use when an Item's summary is not enough. `id` is an Item's `id` from `whats_new`
    or `search`. `text` is the first `max_length` characters (default 10,000), with no
    marker added; `truncated` says whether that left some out and `full_length` gives
    the whole text's length, so call again with a larger `max_length` for the rest.
    If the page cannot be fetched or has no main text, the error gives the Item's
    summary and link instead.
    
whats_newA

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.
    

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: collect_now (force refresh), list_sources (source health), search (stored items query), read_item (full text), whats_new (checkpoint-based new items). The descriptions explicitly carve boundaries, notably between collect_now and whats_new (which auto-collects) and between whats_new and search (which never moves a Checkpoint).

Naming Consistency4/5

Three of five names follow a verb_noun pattern (collect_now, list_sources, read_item), but `search` is a bare verb and `whats_new` follows no verb_noun convention. Still readable and predictable enough to infer behavior.

Tool Count5/5

Five tools is well within a healthy range and each covers a distinct stage of the workflow: source listing, collection, discovery of new items, search, and full-text retrieval. No redundant or filler tools.

Completeness4/5

Core lifecycle (collect, inspect sources, find items, read items, checkpoint tracking) is fully covered with no dead ends. Minor gaps: no source management (add/remove/toggle) and no way to undo or reset a Checkpoint, so agents must work around these.

Maintenance

ActivityNo data
ResponsivenessOutdated data