Skip to main content
Glama
Sign In
sumo-mcp-readonly

sumo-mcp-readonly

by CraigWetzelberger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Find Errors in Sumo Logic

sumo_find_errors

Search recent logs for error indicators like exceptions, failures, and stack traces. Filter by service, text, or source category to isolate issues within a time window.

Instructions

Search for recent errors using an opinionated query that looks for ERROR, exception, failure, fatal, and stack traces.

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

Input Schema

NameRequiredDescriptionDefault
textNoAdditional text to filter for
limitNoMaximum number of results
serviceNoService name to filter by
lastMinutesNoSearch the last N minutes (default: 30)
sourceCategoryNoSource category to search (uses default if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description provides the query terms, which is useful. However, it does not mention return format, pagination, rate limits, or other behavioral traits beyond the search itself.

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?

The description is a single concise sentence that front-loads the purpose and includes specific query terms, with no redundant information.

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?

For a simple search tool with no output schema, the description covers the core behavior and query terms. It is adequate but could mention return results or default behavior more explicitly.

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 coverage is 100%, so parameters are fully documented. The description adds no additional parameter semantics beyond the schema.

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 searches for recent errors using an opinionated query with specific error terms (ERROR, exception, failure, fatal, stack traces). This distinguishes it from the general sumo_search_logs sibling.

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?

The description implies usage for finding errors but does not explicitly compare to sibling tools like sumo_search_logs or state when not to use it. The 'opinionated query' hints at specialization but lacks explicit guidance.

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

Deploy Server

Other Tools