Skip to main content
Glama

Page messages of a search job (non-aggregate; primitive)

sumo_get_messages
Read-only

Page through non-aggregate search job messages with adjustable verbosity, field projection, and deduplication to efficiently examine log results.

Instructions

Pages messages of a NON-aggregate search job (aggregate jobs 400 — use sumo_get_records). Page size max 10000. Partial results are pageable while the job is still gathering. Token levers: detail=summary (whole-job level counts — exact via a side-aggregate, or a labeled sample 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
idYesSearch job id.
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.
limitNoPage size (default 100).
dedupeNoGroup repeated messages globally by (level, signature) — timestamps/UUIDs/hex/numbers are normalized away — and render "first_ts..last_ts LEVEL ×N message".
detailNoOutput verbosity (default compact).
fieldsNoExplicit field projection from the flattened namespace (level/request_id always kept).
formatNoOutput mode (default text).
offsetNoStart offset (default 0).
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?

Annotations already indicate read-only, but description adds significant behavioral context: detail token levers, dedupe behavior (normalizes timestamps/UUIDs/hex/numbers), maxMessageChars safety cap, and that partial results are pageable. 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?

Description is detailed but every sentence adds value. Front-loaded with primary purpose and key constraint. Slightly verbose but well-organized; could be tightened slightly.

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 9 parameters (1 required) and no output schema, description covers all essential aspects: input constraints, behavioral details, parameter explanations, and output format notes. Agent can confidently invoke tool.

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 covers 100% of parameters, description adds meaning beyond schema: explains each detail level (summary/compact/full/raw) with what fields they contain, clarifies sort ordering, dedupe grouping logic, and maxMessageChars purpose. Adds substantial value.

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?

Clearly states it pages messages of non-aggregate search jobs, distinguishes from sumo_get_records for aggregate jobs with a specific error code. Verb 'Pages messages' plus resource context makes purpose unmistakable.

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?

Explicitly tells agent not to use for aggregate jobs (will get 400 error) and suggests sumo_get_records as alternative. Mentions page size max and partial results behavior, giving clear when-to-use guidance.

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