Agentic Dealer Network

Sync catalog changes

inventory_changes

Read-onlyIdempotent

State synchronization for a mirror built from network_snapshot: pass the sync_cursor and receive upserts (current rows in the same view) and tombstones since that position, with has_more and next_cursor. Bounded eventual consistency: take a fresh snapshot at least every 24 hours and whenever resync_required is true. Example: {"cursor": ""}. Pass country=CA for Canadian dealers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`view`	No
`cursor`	Yes
`country`	No	Market to search; rooftops in the other country are excluded. Prices are in that country's currency; the radius stays in miles.	US
`rooftop_slug`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 18, 2026

addedInput schema / properties / country

Added value: +{
+  "default": "US",
+  "description": "Market to search; rooftops in the other country are excluded. Prices are in that country's currency; the radius stays in miles.",
+  "enum": [
+    "US",
+    "CA"
+  ],
+  "type": "string"
+}

addedInput schema / properties / rooftop_slug

Added value: +{
+  "pattern": "^[a-z0-9](?:[a-z0-9-]{0,61}[a-z0-9])?$",
+  "type": "string"
+}

AddedSep 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful context: it discloses the sync pattern (upserts/tombstones, has_more, next_cursor) and the bounded eventual consistency requirement, making behavior transparent beyond annotations.

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?

The description is four sentences with no fluff, front-loading the core purpose, then usage guidance, an example, and a location tip. Every sentence earns its place, and the structure is logical and scannable.

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?

With no output schema, the description adequately explains the return structure (upserts, tombstones, has_more, next_cursor) and the sync flow. It also covers the freshness requirement. However, it does not elaborate on the exact meaning of each view option or how rooftop_slug affects results, but these are reasonably inferable from enums and patterns. Overall, it is complete enough for an agent to call 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 only 25% (only 'country' has a description), so the description must compensate. It clarifies 'cursor' through the example and explains 'country=CA' for Canadian dealers, but it does not explain 'view' or 'rooftop_slug'. While the enums provide some guidance, the lack of descriptions for those two parameters leaves a gap that the schema does not fill.

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 clearly states it is a state synchronization tool for a mirror built from network_snapshot, explaining the cursor-based mechanism with upserts and tombstones. This distinguishes it from siblings like network_snapshot (initial snapshot) and inventory_get (single item fetch) without needing to open schemas.

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 explicitly advises taking a fresh snapshot at least every 24 hours and whenever resync_required is true, which guides when to use this tool vs. alternatives. It also provides a concrete usage example and notes the country parameter for Canadian dealers, leaving no ambiguity about invocation.

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

All Agentic Dealer Network 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.

Resources

Need Help?