Skip to main content
Glama
Sign In

Agentic Web Wiki — standards reference, probe, validate, template

by wiki.agenticweb
OverviewDiscussionsAdmin

changes

Read-onlyIdempotent

List machine-verified specification changes since a YYYY-MM-DD date or ISO-8601 timestamp (newest first, default 50, max 200). Returns { since, count, entries: [{ date, record_id, field, old, new, source }] } filtered optionally by lifecycle step or record_id. Use changes for field-level spec diffs; use stale to audit unverified records or digest for daily ecosystem news.

Input Schema

NameRequiredDescriptionDefault
stepNooptional lifecycle step filter (discover, identify, permit, read, act, coordinate, pay, present, account)
limitNomaximum number of change entries to return (default 50, max 200)
sinceYesYYYY-MM-DD or ISO-8601 timestamp
record_idNooptional standard id or acronym to filter changes (e.g. mcp, a2a, x402)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"maximum number of change entries to return (default 50, max 200)"
    • addedInput schema / properties / record_id / description
      Added value: +"optional standard id or acronym to filter changes (e.g. mcp, a2a, x402)"
    • addedInput schema / properties / step / description
      Added value: +"optional lifecycle step filter (discover, identify, permit, read, act, coordinate, pay, present, account)"
    • addedInput schema / properties / step / enum
      Added value: +[
+  "discover",
+  "identify",
+  "permit",
+  "read",
+  "act",
+  "coordinate",
+  "pay",
+  "present",
+  "account"
+]
    • removedInput schema / properties / step / maxLength
      Removed value: -40
  2. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"YYYY-MM-DD, or an ISO-8601 timestamp (its offset is applied, then the UTC date is used)"New value: +"YYYY-MM-DD or ISO-8601 timestamp"
  3. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"YYYY-MM-DD; a full ISO-8601 timestamp is accepted and cut to the date"New value: +"YYYY-MM-DD, or an ISO-8601 timestamp (its offset is applied, then the UTC date is used)"
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context on top: newest-first ordering, default 50 / max 200 caps, and the option to narrow by lifecycle step or record_id. It stops short of noting pagination beyond the limit or any rate behavior.

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?

Three sentences, front-loaded with the core action and scope, then return shape, then sibling routing. Nothing is redundant and no sentence could be dropped without losing an agent-relevant fact.

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, and the description compensates by spelling out the exact response shape (since, count, entries with date/record_id/field/old/new/source). Combined with filters, ordering, and limits, an agent has everything needed to call it correctly.

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%, with descriptions and an enum already on every property, so the schema carries the parameter burden. The description restates the since format and the limit bounds rather than adding new meaning; only the mention of combining filters is marginal added value.

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?

The description opens with a specific verb and resource — 'List machine-verified specification changes' — plus the ordering and default page size. It explicitly distinguishes itself from siblings by naming stale and digest as the tools for different questions.

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?

It gives an explicit routing rule: 'Use changes for field-level spec diffs; use stale to audit unverified records or digest for daily ecosystem news.' Both alternatives are named with the condition that selects them, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agentic Web Wiki — standards reference, probe, validate, template toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources