Skip to main content
Glama

Run a Sumo Logic search (create → wait → fetch → delete)

sumo_run_search
Read-only

Execute a Sumo Logic search query, wait for completion, return first N results, and auto-delete the job. Supports relative or absolute time ranges and varying verbosity levels.

Instructions

Workhorse: creates a Sumo Logic search job, waits for completion, returns the first N results, and deletes the job. Time range: exactly ONE of last (relative, e.g. "15m", "2h"; units s/m/h/d) OR both from and to (ISO-8601 like 2026-07-02T18:28:00, or epoch milliseconds). 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. Inline limit max 5000 — use sumo_export_results for bulk (up to 100k to a file).

Scoping in one line: filter WHERE with _sourcecategory=. Severity schemas VARY per system — let sumo_error_digest auto-detect (it discloses what it applied), or run sumo_describe_schema on a new scope and pass filter=. TRACE one request by searching its quoted correlation id with no other filters. Hostname keywords match only request logs — hunt errors by _sourcecategory. Full workflow: the "triage" MCP prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd time: ISO-8601 or epoch ms. Requires `from`.
fromNoStart time: ISO-8601 or epoch ms. Requires `to`.
lastNoRelative window ending now, e.g. "15m", "2h", "1d". Mutually exclusive with from/to.
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.
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).
extractNoOptional per-field JSON extraction: alias → path under _raw, e.g. {"status":"log.status","user":"log.context.user"}. Appends one `| json field=_raw "<path>" as <alias> nodrop` clause per entry (chained; never the broken comma multi-extract form). Aliases must be simple identifiers; non-aggregate queries only. Extracted aliases join the flattened field namespace (combine with `fields` or ndjson/export lines).
keepJobNoKeep the job alive after returning (server keeps it polled; use the primitives to page more). Idle kept jobs are auto-deleted after ~10 minutes (YOKOZUNA_KEEPALIVE_IDLE_MINUTES); any access (status/messages/records) resets the idle timer.
timeZoneNoIANA timezone for query-time parsing (default UTC).
byReceiptTimeNoSearch by receipt time; recommended true for very recent windows (ingestion lag).
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?

Discloses the full lifecycle (create, wait, fetch, delete), idle timeout for kept jobs (~10 minutes), side-aggregate for detail=summary with provenance disclosure, token levers for detail levels, and the fact that sort only orders the returned set. This is rich behavior context beyond the annotations. However, note that annotations claim readOnlyHint: true, but the description describes mutation (create/delete), creating a contradiction.

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 description is detailed and well-structured with paragraphs and bullet-like formatting. It is front-loaded with the main action. However, it is quite long (several sentences) and might be dense for an agent. Could be slightly more concise without losing critical information, but every sentence serves a purpose.

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?

Despite no output schema, the description explains return formats (summary/compact/full/raw) and behavior like dedupe grouping. It covers time range, scoping, and references sibling tools. With 15 parameters, it provides adequate context for using the tool effectively. The lifecycle, limits, and edge cases are well addressed.

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?

Schema has 100% coverage with descriptions, but the description adds significant meaning: explains time range options (mutual exclusivity), token levers for detail (summary/compact/full/raw with details), dedupe behavior, keepJob lifecycle, maxMessageChars as safety cap, fields as projection, extract as JSON extraction, sort limitations, etc. Provides context that schema alone does not.

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's purpose: 'creates a Sumo Logic search job, waits for completion, returns the first N results, and deletes the job.' It distinguishes itself from siblings by mentioning sumo_export_results for bulk and sumo_error_digest for auto-detection of severity. The title 'Run a Sumo Logic search (create → wait → fetch → delete)' is also very specific.

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: 'Inline limit max 5000 — use sumo_export_results for bulk (up to 100k to a file).' Also recommends using sumo_error_digest or sumo_describe_schema for severity detection and mentions the 'triage' MCP prompt for full workflow. Clear when to use alternatives.

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