Skip to main content
Glama

recent_changes

Recent platform changes, newest first.

platform: filter by platform (apple, android, google-play, github, vercel, cloudflare, expo, supabase, firebase). tag: filter by heuristic tag (deprecation, breaking, deadline, policy, security, pricing). days: look-back window (max 90). limit: max items (max 50). Summaries are truncated; use get_change for full text. min_importance: "low" (everything), "medium" or "high" to drop routine release noise. Importance is AI-rated or heuristic (see importance_basis). by: "published" (default) or "updated", which also surfaces old posts the vendor edited recently.

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
byNopublished
tagNo
daysNo
limitNo
platformNo
min_importanceNolow

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / by
      Added value: +{
      +  "default": "published",
      +  "title": "By",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly does so: it discloses that summaries are truncated, that importance is 'AI-rated or heuristic (see importance_basis)', and that by='updated' surfaces older posts edited recently. It omits any note on rate limits or auth, but the behavioral picture is well above the norm for an unannotated tool.

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-loads the one-line purpose, then one line per parameter, then a routing pointer to get_change. Dense and largely waste-free, though the parameter dump reads as a flat list rather than being prioritized by importance.

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 six-param list tool with an output schema present, the description covers filtering, ordering, bounds, and truncation behavior sufficiently. Nothing critical is missing for correct invocation, though the lack of sibling differentiation keeps it short of fully complete.

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 do all the work, and it does: every one of the six parameters is defined with meaning, bounds (days max 90, limit max 50), and enumerated values (platform list, tag list, min_importance levels). It even supplies enum context the schema lacks entirely.

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?

States a specific verb+resource ('Recent platform changes, newest first') with a clear ordering guarantee. It does not distinguish itself from the sibling search_changes, which retrieves a similar resource, so an agent still has to infer the boundary between the two.

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?

It routes the agent to get_change for full text and explains what min_importance is for ('drop routine release noise'), which is genuine conditional guidance. However, it never says when to prefer this tool over search_changes or weekly_digest, leaving the main routing decision unaddressed.

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