Skip to main content
Glama

Contrie

by com.contrie
OverviewDiscussionsAdmin

Read what a monitor has seen

contrie_changes
Read-only

Read a monitor's history: its latest answer with evidence status and the last 20 events (baseline, change, error). Pass nextCursor as before for older events, or eventId to recover one exact event; do not combine them. Also returns monitor.runStatus for one current original slot: scheduled (future with no outstanding work), pending (work may still complete or publish), needs_review (reason result_unconfirmed or result_unavailable), or unknown (ambiguous evidence, including a recent stopped claim whose request ownership cannot be proved). Each object includes scheduledFor, the UTC millisecond due time; only needs_review includes reason. Stopped idle runStatus is null only with complete positive no-outstanding current-slot evidence. statusRead {coverage: complete, observedAt} covers the monitor/status database statement observation, not separately read events or fleet/history counts. Pending promises no running process, charge, completion time or recovery; review reasons imply neither refund, failed extraction nor semantic correctness. Snapshot failure is SERVICE_UNAVAILABLE. Reading does not change monitoring or accounting state; ordinary authentication and rate-limit effects apply. Every change carries the full before and after responses with evidence, and a diff of the fields that moved. Charges no credits. Requires authentication: sign in with your Contrie account (OAuth), or send an API key in the Authorization header.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe monitor id
beforeNonextCursor from the previous page; omit for the latest 20 events
eventIdNoAn exact retained event ID from this monitor or its webhook; do not combine with before

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / before
      Added value: +{
+  "description": "nextCursor from the previous page; omit for the latest 20 events",
+  "type": "string"
+}
    • addedInput schema / properties / eventId
      Added value: +{
+  "description": "An exact retained event ID from this monitor or its webhook; do not combine with before",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The monitor id from contrie_watch"New value: +"The monitor id"
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Well beyond the readOnly/openWorld annotations, it discloses auth requirements (OAuth or API key in Authorization), rate-limit effects, that reading does not mutate monitoring or accounting state, that it charges no credits, and that snapshot failure surfaces as SERVICE_UNAVAILABLE. It also carefully scopes the statusRead coverage claim to the monitor/status statement only, which prevents over-reading the evidence.

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 core purpose is front-loaded and most sentences carry distinct semantics (runStatus states, statusRead scope, event diff contents). It is dense and includes some defensive hedging ('Pending promises no running process, charge...') that borders on legal boilerplate, keeping it just short of a 5.

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?

With no output schema, the description carries the full burden of explaining the return shape — runStatus values and their meanings, statusRead coverage, and the before/after evidence diff on every change — and it does so thoroughly. An agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the schema documents all three params; the description adds real value on top by clarifying the mutual exclusion of before/eventId and the recovery semantics of each. It stops short of name-level detail but meaningfully augments the schema.

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 opens with a specific verb+resource ('Read a monitor's history') and enumerates what comes back (latest answer with evidence status, last 20 events of baseline/change/error). This is far more concrete than its generic-name siblings, but it never names or contrasts with contrie_read, contrie_search, or contrie_verify, so an agent must infer which read tool fits.

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?

It gives clear when-to-use guidance for its own parameters — pass nextCursor as before for older events, or eventId to recover one exact event, and do not combine them. However, it offers no routing advice against the overlapping sibling read tools (contrie_read, contrie_search), so tool-selection guidance is only implied.

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

All Contrie toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources