Skip to main content
Glama

spec_changes_since

Read-onlyIdempotent

Returns what changed in the MCP and A2A specifications since a date, each as a short summary in our own words with a link to the release notes. A short curated list, not a full changelog. Example output: {"since":"2026-01-01","count":4,"changes":[{"spec":"MCP specification","tag":"2026-07-28"}]}. Optional argument: date as YYYY-MM-DD, for example "2026-01-01". With no arguments it starts on 1 January of the snapshot year. Good for 'What changed in the MCP spec this year?'.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD, for example "2026-01-01". Optional: empty means 1 January of the snapshot year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / date / default
      Added value: +""
    • addedInput schema / properties / date / description
      Added value: +"Date as YYYY-MM-DD, for example \"2026-01-01\". Optional: empty means 1 January of the snapshot year."
    • addedInput schema / properties / date / examples
      Added value: +[
      +  "2026-01-01"
      +]
    • removedInput schema / required
      Removed value: -[
      -  "date"
      -]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: the curated (non-exhaustive) nature of the list, the shape of the response, and the default when the argument is omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the date format and default are restated verbatim from the schema, and the inline JSON example plus the closing usage sentence make the text longer than needed for a one-optional-parameter tool.

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?

A single optional parameter, annotations covering safety, and an example response in lieu of an output schema leave nothing an agent needs missing. The default-when-empty behavior is spelled out explicitly.

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 100% and the schema already documents the YYYY-MM-DD format and the empty-means-January-1 default. The description merely restates that format and default, adding no new semantics.

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?

States a specific verb and resource ('Returns what changed in the MCP and A2A specifications since a date') plus the output form (short summaries with links). It also bounds the scope ('A short curated list, not a full changelog'), which no sibling tool duplicates, so an agent can select it without opening the schema.

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?

Gives a concrete invocation cue ('Good for "What changed in the MCP spec this year?"') and clarifies that no-date calls default to 1 January of the snapshot year. It does not name alternatives or explicitly say when not to use it, but no sibling overlaps this purpose.

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