Skip to main content
Glama

Recent status changes and news feed

recent_changes
Read-onlyIdempotent

Latest status changes in the registry (last 90 days, with source) and the latest items of DiscoverIA's feed (last 30 days: sciences, models and labs, apps, devices).

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

Input Schema

NameRequiredDescriptionDefault
kindNo'status' for status changes only, 'feed' for feed items only, 'all' for both. Default 'all'.all
langNoLanguage of titles, labels and texts: 'fr' (French) or 'en' (English). Default 'en'. Use the user's language.en
limitNoMaximum items per list, 1 to 50. Default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and openWorldHint=false. The description adds useful behavioral context by specifying recency windows (90 days for status, 30 days for feed), inclusion of sources, and feed categories. It does not describe return format or pagination, but the annotations cover the safety profile well.

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?

The description is a single front-loaded sentence with no filler. It efficiently communicates both data sources, their time windows, and the feed categories.

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 read-only, optional-parameter tool with no output schema, the description supplies key context: freshness windows and feed categories. The schema covers parameter semantics and annotations cover safety, so the remaining gap around exact return structure is minor.

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%, and the schema fully documents all three parameters, including enums and defaults. The description adds context about the feed categories but does not add meaning beyond the schema for kind, lang, or limit; baseline 3 is appropriate.

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 specific resource and scope: latest registry status changes within 90 days plus DiscoverIA feed items within 30 days across named categories. It is clear what the tool returns, though it does not explicitly distinguish itself from siblings such as list_statuses or search_announcements.

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?

The description provides no guidance on when to use this tool versus alternatives like list_statuses, get_announcement, or search_announcements. It also gives no exclusions or conditions for choosing the status-only, feed-only, or combined mode beyond what the schema already documents.

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