Skip to main content
Glama

What arrived since the last poll (stateless cursor monitor)

sumo_new_since
Read-only

Poll Sumo Logic for log messages that arrived since the previous call, returning a cursor for the next request. Provides gap-free, duplicate-free results using receipt-time windows.

Instructions

Stateless receipt-time monitor for polling loops: returns messages that ARRIVED since your last call plus a new cursor. First call: omit since to get a baseline over lookback (default "15m"). Every response contains a cursor=<epoch ms> line — pass that value as since on the next call and the half-open windows [since, now−settleMargin) tile contiguously with no gaps or duplicates. byReceiptTime is FORCED true and the window ends 180s in the past (settle margin) so late-arriving logs are not skipped — results are complete but ~180s stale. Aggregate queries (| count …) are rejected — use sumo_run_search for those. Token levers: detail=summary (whole-job counts by the AUTO-DETECTED severity field — exact via a side-aggregate with disclosed provenance, or a loud SAMPLE label if that fails — plus a compact histogram and top message signatures; cheapest) | compact (timestamp, level, request_id, _sourcecategory, FULL message, plus method/path/status when present) | full (compact + duration_s/logger/client_ip) | raw (verbatim _raw — logs exactly as the app emitted them, including anything sensitive it logged). See the fields/dedupe/maxMessageChars params for projection, grouping, and the message-length cap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOrder of returned messages by _messagetime (default "asc" = oldest→newest, best for tracing). Client-side: orders only the RETURNED result set — raise limit or narrow the query for full ordering. Not applicable to aggregate records.
limitNoMax inline results (default 100, hard max 5000).
queryYesSumo Logic query text (NON-aggregate — raw messages only).
sinceNoCursor from the previous sumo_new_since response (epoch ms). Omit on the first call.
dedupeNoGroup repeated messages within the RETURNED page by (level, signature) — timestamps/UUIDs/hex/numbers are normalized away — rendering "first_ts..last_ts LEVEL ×N message". Raise limit for broader grouping (only fetched rows are grouped). With detail:"raw", each group keeps one verbatim _raw exemplar.
detailNoOutput verbosity (default compact).
fieldsNoExplicit field projection from the flattened namespace (level/request_id always kept).
formatNoOutput mode (default text).
lookbackNoBaseline window when `since` is absent, e.g. "15m", "1h" (units s/m/h/d; default "15m").
maxMessageCharsNoSafety cap for the message field (default 10000); the message is never truncated by default.
Behavior5/5

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

Beyond annotations (readOnlyHint=true), description discloses forced byReceiptTime, 180s settle margin, ~180s staleness, and aggregate rejection. No contradictions.

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?

Dense but well-structured, front-loading core concept. A bit verbose in sections (e.g., detail enumeration), but every sentence adds value for a complex tool.

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?

Given 10 parameters and no output schema, the description covers window semantics, cursor use, detail levels, dedupe, field projection, and more. Sufficient for an agent to use correctly.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds deep context: detail modes (summary/compact/full/raw) with exact contents, dedupe mechanism, lookback default, and maxMessageChars safety cap. Greatly enhances understanding.

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 the tool is a 'stateless receipt-time monitor for polling loops' that returns messages that arrived since the last call plus a cursor. It explicitly distinguishes from siblings like sumo_run_search by rejecting aggregate queries.

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?

Provides explicit guidance: first call omit 'since', how to pass cursor, window semantics, rejection of aggregate queries, and alternative tool (sumo_run_search). Clear when-to-use and when-not.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mbe24/yokozuna-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server