Skip to main content
Glama

Changes since a date

get_changes
Read-onlyIdempotent

Use when the user asks what changed in the servers they use, or wants to review tool changes before using a server again. Tools added or removed, input schema and description changes, new destructive tools, servers that stopped or started answering, new listings, and changes in authentication, MCP version, server version or HTTPS (before and after), per day for the last 30 days. Facts, not verdicts. Give names to watch specific servers.

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

Input Schema

NameRequiredDescriptionDefault
namesNo
sinceNoYYYY-MM-DD, e.g. 2026-10-01; default yesterday

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / since / description
      Previous value: -"YYYY-MM-DD, default yesterday"New value: +"YYYY-MM-DD, e.g. 2026-10-01; default yesterday"
    • addedInput schema / properties / since / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: a fixed 30-day window, per-day granularity, before/after values for auth/version/HTTPS, and the stance that results are facts without verdicts. It adds context beyond the structured fields, though it says nothing about result size or limits.

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?

The usage trigger is front-loaded and the short 'Facts, not verdicts' line conveys the result character efficiently. The long middle enumeration of change types is a single dense run-on sentence that is informative but heavier than necessary; it could be itemized or trimmed without losing meaning.

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?

With no output schema, the description carries the return-value burden and does so by listing the change categories and noting before/after values. For a 2-parameter read tool this is nearly complete; the gaps are how results are scoped when `names` is omitted and how the 30-day window interacts with the `since` default.

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 coverage is 50%, so the schema already documents the `since` format and default. The description does add real meaning for `names` — 'Give names to watch specific servers' explains intent where the schema only says 'Registry name'. But it also creates ambiguity: it says data spans the last 30 days while the schema default for `since` is yesterday, leaving unclear what the default query actually returns. Baseline 3.

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 names the resource (changes in servers the user relies on) and enumerates the concrete change categories returned: tools added/removed, schema and description edits, new destructive tools, availability, auth, MCP/server version, HTTPS. That is far more specific than the title. It does not, however, distinguish itself from the sibling get_server_history, which an agent could easily confuse with it.

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

Usage Guidelines4/5

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

It opens with explicit trigger conditions: reviewing what changed in servers the user uses, or checking tool changes before reusing a server. That is clear when-to-use guidance. It stops short of naming an alternative such as get_server_history or stating when not to use it, so it earns a 4 rather than a 5.

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