INITE Atlas

What moved in the AI tools market

atlas_changes

Read-onlyIdempotent

What changed among the tools in the INITE Atlas: prices up or down, free plans added or dropped, OpenAPI specs published, MCP servers listed. Each change was read twice from the vendor's own page or the public registry before it counts, and a correction somebody typed in is never reported as the vendor's move. Each list says how many tools were in a position to change at all and how many moved. domain asks about one tool.

Input Schema

Name	Required	Description
`days`	No	How far back, default 30
`limit`	No	Changes in each list per page, default 25
`domain`	No	Only this tool, e.g. elevenlabs.io
`offset`	No	The nextOffset of the previous answer

Output Schema

Name	Required	Description	Default
`since`	Yes
`domain`	No
`pricing`	No
`interfaces`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 3, 2026

addedInput schema / properties / domain

Added value: +{
+  "description": "Only this tool, e.g. elevenlabs.io",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Changes in each list per page, default 25",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "The nextOffset of the previous answer",
+  "minimum": 0,
+  "type": "number"
+}

addedOutput schema / properties / domain

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / interfaces / properties

Added value: +{
+  "limit": {
+    "type": "integer"
+  },
+  "matched": {
+    "type": "integer"
+  },
+  "moved": {
+    "type": "array"
+  },
+  "nextOffset": {
+    "type": [
+      "integer",
+      "null"
+    ]
+  },
+  "offset": {
+    "type": "integer"
+  },
+  "readTwice": {
+    "type": "number"
+  },
+  "total": {
+    "type": "integer"
+  },
+  "totalIsAtLeast": {
+    "type": "boolean"
+  }
+}

addedOutput schema / properties / interfaces / required

Added value: +[
+  "matched",
+  "total",
+  "moved"
+]

addedOutput schema / properties / pricing / properties

Added value: +{
+  "limit": {
+    "type": "integer"
+  },
+  "matched": {
+    "type": "integer"
+  },
+  "moved": {
+    "type": "array"
+  },
+  "nextOffset": {
+    "type": [
+      "integer",
+      "null"
+    ]
+  },
+  "offset": {
+    "type": "integer"
+  },
+  "readTwice": {
+    "type": "number"
+  },
+  "total": {
+    "type": "integer"
+  },
+  "totalIsAtLeast": {
+    "type": "boolean"
+  }
+}

addedOutput schema / properties / pricing / required

Added value: +[
+  "matched",
+  "total",
+  "moved"
+]

First observedOct 16, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the read-only and non-destructive annotations, it discloses meaningful provenance and inclusion behavior: changes are checked twice against vendor pages or public registries, and manually entered corrections are not presented as vendor actions. It also explains that lists include both the eligible population and the number that changed, helping the agent interpret the feed's scope.

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 purpose and event types are front-loaded, followed by verification behavior and a short filtering note. The verification sentence is somewhat wordy and conversational, but the paragraph remains compact and contains little filler.

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?

Together with the fully described parameters, safety annotations, and output schema, the description supplies what an agent needs to invoke and interpret this read-only change feed. Event coverage, validation policy, correction handling, and single-tool filtering are all addressed without needing to duplicate return-field documentation.

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 description coverage is 100%, so the schema already documents the time window, pagination, and domain filter. Saying that `domain` asks about one tool is useful but adds little beyond the schema's existing explanation and example.

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 clearly identifies a feed of changes to tools in the INITE Atlas and enumerates concrete event types, including pricing, free plans, OpenAPI specs, and MCP servers. It does not explicitly distinguish this feed from siblings such as atlas_dataset_changes or atlas_lookup.

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?

The opening establishes the context for use—reviewing market or vendor changes—and the final sentence explains that `domain` narrows the request to one tool. There is no explicit when-not guidance or routing to an alternative sibling.

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

All INITE Atlas tools Inspect

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.