Skip to main content
Glama

What changed since a date

changes_since
Read-onlyIdempotent

Everything recorded since a date, for a model whose knowledge ends at a cutoff: price changes, new items, removals and retirements, newest first, each with its UTC date, the previous good snapshot, the source URL and a permanent link to the item. counts are for the whole period (not just the page); gaps names the sources that are stopped now, with the day they stopped (never filled in; outages that recovered are not recorded); record_begins says how far back the record goes. summary=true returns the largest percent moves per category (at most 40 entries) in one answer, ordered by size of the move, not by price. Paging: pass next_cursor back as cursor. Entries carry recorded values only, never a current price. Returns an error object for a bad date or filter. Same data as GET /v1/changes-since. Use this one to page through every entry or to filter by category and kind (price_change, new_item, removed_or_stopped, retirement); for a first look at what changed since your cutoff, with counts, scope llm/gpu/vps and the gaps, call what_changed_since instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "since": "<since>"
    },
    "name": "changes_since"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoprice_change, new_item, removed_or_stopped or retirement
limitNoMaximum entries per page, 1 to 1000
sinceYesUTC date, YYYY-MM-DD, e.g. the day your knowledge ends
cursorNonext_cursor of the previous page
summaryNotrue = the largest moves per category in one answer
categoryNovps, gpu, llm, inference or media
providerNoProvider slug, e.g. vultr, openai

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this as a safe read-only, idempotent operation, but the description adds substantial behavior: newest-first ordering, fields returned per entry, counts covering the whole period, gaps semantics for stopped sources, record_begins, summary limits and ordering, recorded values only rather than current prices, and an error object for bad filters.

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 description is front-loaded with the core purpose and every clause is mostly useful, but it is a dense single paragraph with many semicolon-separated details. It is efficient for the tool's complexity, though the structure could be easier to scan.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly: entry fields, whole-period counts, gaps, record_begins, summary entry cap and ordering, paging, recorded-only values, and error behavior. An agent has enough information to invoke and interpret this tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all seven parameters, but the description still adds meaning: since is framed as the knowledge cutoff, cursor is explained through next_cursor paging, summary=true is described in detail, and category/kind filtering is called out. It does not add much for provider or limit beyond the schema, so this is strong but not perfect.

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?

Opens with a specific verb and resource: everything recorded since a date, then enumerates price changes, new items, removals and retirements. It explicitly contrasts itself with what_changed_since, so an agent can tell the two apart from the description alone.

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?

Explicitly says to use this tool to page through every entry or to filter by category and kind, and says to call what_changed_since instead for a first look with counts, scope llm/gpu/vps and gaps. It also gives the paging instruction to pass next_cursor back as cursor.

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