Skip to main content
Glama
Sign In

OneLence

by com.onelence
OverviewDiscussionsAdmin

Recorded changes

onelence_list_changes
Read-onlyIdempotent

Business changes the team recorded (budget, offer, pricing, tracking, creative, campaign, partner), newest first; pass start and end for the changes made in a period. Use it to explain what changed around a date; OneLence never states a change's impact.

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

Input Schema

NameRequiredDescriptionDefault
endNoOnly changes made up to this date (inclusive) or ISO 8601 date-time.
siteNoSite domain (e.g. example.com) or site id. Defaults to the workspace's newest active site.
limitNoItems to return (default 10).
startNoOnly changes made on or after this date (YYYY-MM-DD) or ISO 8601 date-time. Without it, every change.
cursorNonext_cursor from the previous call, for more.

Output Schema

NameRequiredDescriptionDefault
dataYes
moreNoHow to fetch the next page, when has_more.
noteYes
objectYes
has_moreYes
unreadableYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / end
      Added value: +{
+  "description": "Only changes made up to this date (inclusive) or ISO 8601 date-time.",
+  "maxLength": 40,
+  "type": "string"
+}
    • addedInput schema / properties / start
      Added value: +{
+  "description": "Only changes made on or after this date (YYYY-MM-DD) or ISO 8601 date-time. Without it, every change.",
+  "maxLength": 40,
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "properties": {
+          "affected_sources": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "category": {
+            "anyOf": [
+              {
+                "enum": [
+                  "budget_change",
+                  "campaign_change",
+                  "creative_change",
+                  "partner_change",
+                  "email_campaign",
+                  "social_post",
+                  "pricing_change",
+                  "offer_change",
+                  "tracking_change",
+                  "site_launch",
+                  "tv_radio_ad",
+                  "outdoor_ad",
+                  "influencer_campaign",
+                  "press_coverage",
+                  "event_sponsorship",
+                  "other"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "ends_on": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "family": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "image_url": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "label": {
+            "type": "string"
+          },
+          "link_url": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "markets": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "note": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "object": {
+            "const": "recorded_change",
+            "type": "string"
+          },
+          "observation_scope": {
+            "enum": [
+              "target",
+              "portfolio"
+            ],
+            "type": "string"
+          },
+          "observation_state": {
+            "enum": [
+              "not_eligible",
+              "observation_pending",
+              "observation_ready",
+              "insufficient_evidence",
+              "dependency_unavailable"
+            ],
+            "type": "string"
+          },
+          "occurred_at": {
+            "type": "string"
+          },
+          "quantified_change": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "recorded_at": {
+            "type": "string"
+          },
+          "target": {
+            "properties": {
+              "kind": {
+                "enum": [
+                  "source",
+                  "source_family",
+                  "source_set",
+                  "portfolio"
+                ],
+                "type": "string"
+              },
+              "label": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "label"
+            ],
+            "type": "object"
+          },
+          "timezone": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "object",
+          "id",
+          "label",
+          "occurred_at",
+          "timezone",
+          "target",
+          "observation_scope",
+          "affected_sources",
+          "family",
+          "category",
+          "ends_on",
+          "image_url",
+          "link_url",
+          "markets",
+          "quantified_change",
+          "note",
+          "recorded_at",
+          "observation_state"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "more": {
+      "description": "How to fetch the next page, when has_more.",
+      "type": "string"
+    },
+    "next_cursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "object": {
+      "const": "list",
+      "type": "string"
+    },
+    "unreadable": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "object",
+    "data",
+    "has_more",
+    "next_cursor",
+    "note",
+    "unreadable"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely new behavioral context: results are ordered newest first and, importantly, 'OneLence never states a change's impact' — a real limitation an agent could otherwise mis-assume. It does not mention pagination behavior (limit/cursor) despite exposing those parameters.

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?

Two dense sentences with zero filler: the first states scope, categories and ordering; the second states the use case and the key limitation. The most decision-relevant facts are front-loaded.

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 an output schema present, return values need no explanation, and the description covers scope, ordering and the impact caveat. Minor omission: nothing explains pagination flow or the default-site fallback, though the schema handles the latter.

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 every parameter is already documented, including the 'without start, every change' semantics. The description reinforces the start/end pairing as a period filter but adds no format examples, defaults, or cursor/limit guidance beyond the schema. Baseline 3 applies.

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?

Names the resource precisely ('business changes the team recorded') and enumerates the change categories covered (budget, offer, pricing, tracking, creative, campaign, partner), plus the ordering (newest first). It implicitly separates itself from the write-side sibling onelence_record_change, though it never names that sibling explicitly.

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?

'Use it to explain what changed around a date' gives a concrete usage scenario and the start/end parameters are framed as the period filter. No explicit when-not-to-use or named alternatives (e.g. list_decisions, list_signals) are given, so it stops short of full routing guidance.

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

All OneLence toolsInspect
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