Sourcey

Get changes

get_changes

Read-onlyIdempotent

Track added, changed, withdrawn, and removed startup credits, discounts, free tiers, perks, and deals through Sourcey's signed change feed after an optional cursor.

Input Schema

Name	Required	Description	Default
`cursor`	No	Opaque signed cursor returned by the previous change-feed page.

Output Schema

Name	Required	Description	Default
`data`	Yes
`release_id`	Yes
`diff_digest`	Yes
`next_cursor`	Yes
`snapshot_id`	Yes
`feed_contract`	Yes
`retained_from_release_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026
- addedOutput schema / properties / data / items / properties / tombstone / properties / canonical_route / format
```
Added value: +"starts_with"
```

Changed1 schema field changedSep 28, 2026

changedOutput schema / properties / data / items / properties / kind / examples

Previous value: -[
-  "entity.added",
-  "entity.updated",
-  "entity.retired",
-  "program.added",
-  "program.updated",
-  "program.retired",
-  "offer.added",
-  "offer.updated",
-  "offer.ended",
-  "offer.retired",
-  "offer.withdrawn",
-  "policy.added",
-  "policy.updated",
-  "policy.retired",
-  "agent-readiness.added",
-  "agent-readiness.updated",
-  "agent-readiness.regraded",
-  "agent-readiness.ended",
-  "agent-readiness.withdrawn",
-  "asset.bound",
-  "asset.updated",
-  "asset.withdrawn"
-]New value: +[
+  "entity.added",
+  "entity.updated",
+  "entity.retired",
+  "program.added",
+  "program.updated",
+  "program.retired",
+  "offer.added",
+  "offer.updated",
+  "offer.ended",
+  "offer.retired",
+  "offer.withdrawn",
+  "policy.added",
+  "policy.updated",
+  "policy.retired",
+  "agent-readiness.added",
+  "agent-readiness.updated",
+  "agent-readiness.regraded",
+  "agent-readiness.relocated",
+  "agent-readiness.ended",
+  "agent-readiness.withdrawn",
+  "asset.bound",
+  "asset.updated",
+  "asset.withdrawn"
+]

Changed2 schema fields changedAug 5, 2026

changedOutput schema / properties / data / items / properties / kind / examples

Previous value: -[
-  "entity.added",
-  "entity.updated",
-  "entity.retired",
-  "program.added",
-  "program.updated",
-  "program.retired",
-  "offer.added",
-  "offer.updated",
-  "offer.ended",
-  "offer.retired",
-  "offer.withdrawn",
-  "policy.added",
-  "policy.updated",
-  "policy.retired",
-  "adoption.added",
-  "adoption.updated",
-  "adoption.regraded",
-  "adoption.ended",
-  "adoption.withdrawn",
-  "asset.bound",
-  "asset.updated",
-  "asset.withdrawn"
-]New value: +[
+  "entity.added",
+  "entity.updated",
+  "entity.retired",
+  "program.added",
+  "program.updated",
+  "program.retired",
+  "offer.added",
+  "offer.updated",
+  "offer.ended",
+  "offer.retired",
+  "offer.withdrawn",
+  "policy.added",
+  "policy.updated",
+  "policy.retired",
+  "agent-readiness.added",
+  "agent-readiness.updated",
+  "agent-readiness.regraded",
+  "agent-readiness.ended",
+  "agent-readiness.withdrawn",
+  "asset.bound",
+  "asset.updated",
+  "asset.withdrawn"
+]

changedOutput schema / properties / data / items / properties / subject_type / enum

Previous value: -[
-  "entity",
-  "program",
-  "offer",
-  "policy",
-  "adoption_profile",
-  "asset_binding"
-]New value: +[
+  "entity",
+  "program",
+  "offer",
+  "policy",
+  "agent_readiness_profile",
+  "asset_binding"
+]

Changed1 schema field changedAug 4, 2026
- addedInput schema / properties / cursor / description
```
Added value: +"Opaque signed cursor returned by the previous change-feed page."
```

Changed5 schema fields changedJul 30, 2026

addedOutput schema / properties / data / items / properties / kind / description

Added value: +"Append-only release change kind. Known values are examples; new kinds may appear within public API v1."

removedOutput schema / properties / data / items / properties / kind / enum

Removed value: -[
-  "entity.added",
-  "entity.updated",
-  "entity.retired",
-  "program.added",
-  "program.updated",
-  "program.retired",
-  "offer.added",
-  "offer.updated",
-  "offer.ended",
-  "offer.withdrawn",
-  "policy.added",
-  "policy.updated",
-  "policy.retired",
-  "adoption.added",
-  "adoption.updated",
-  "adoption.regraded",
-  "adoption.ended",
-  "adoption.withdrawn",
-  "asset.bound",
-  "asset.updated",
-  "asset.withdrawn"
-]

addedOutput schema / properties / data / items / properties / kind / examples

Added value: +[
+  "entity.added",
+  "entity.updated",
+  "entity.retired",
+  "program.added",
+  "program.updated",
+  "program.retired",
+  "offer.added",
+  "offer.updated",
+  "offer.ended",
+  "offer.retired",
+  "offer.withdrawn",
+  "policy.added",
+  "policy.updated",
+  "policy.retired",
+  "adoption.added",
+  "adoption.updated",
+  "adoption.regraded",
+  "adoption.ended",
+  "adoption.withdrawn",
+  "asset.bound",
+  "asset.updated",
+  "asset.withdrawn"
+]

addedOutput schema / properties / data / items / properties / kind / pattern
```
Added value: +"^[a-z][a-z0-9-]*(?:\\.[a-z][a-z0-9-]*)+$"
```
addedOutput schema / properties / data / items / properties / kind / x-sourcey-extensible-enum
```
Added value: +true
```

First observedJul 30, 2026

TDQS

A4/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 behavior, so the safety profile is covered. Beyond that, the description adds that the feed is 'signed' (integrity/authenticity context) and what categories of change it emits, which is genuine added value. It stops short of describing ordering, page size, or how the feed terminates.

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?

One sentence, front-loaded on the verb and the core resource, with no filler. The enumeration of change types and entity types is dense but each item serves to scope what the feed returns.

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?

An output schema exists, so return values and cursor shape need not be explained here, and annotations carry the safety profile. The description covers scope and entity breadth adequately; only paging/ordering details are absent, which is a minor gap for a change-feed tool.

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?

With a single parameter at 100% schema coverage, the schema already explains that cursor is an opaque signed value from the previous page. The description only adds that the cursor is optional, which is marginal beyond the structured field, so the baseline 3 applies.

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 (track) and resource (Sourcey's signed change feed), and enumerates both the change kinds (added, changed, withdrawn, removed) and the entity types covered (credits, discounts, free tiers, perks, deals). This framing is unmistakably distinct from the search/compare siblings, so an agent can select it without opening a schema.

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

Usage Guidelines3/5

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

The phrase 'after an optional cursor' implies this is a paging/polling endpoint, which is useful implied usage guidance. However, it never states when to call this versus search_offers or compare_offers, nor when to omit the cursor (first page), so guidance is only inferred.

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

All Sourcey tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.