Skip to main content
Glama
Sign In
nimbus

nimbus

by nimbus-agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getRecentIncidents

Retrieve recent incidents from the local index, ordered newest first. Filter by service to find incidents affecting a specific system.

Instructions

List recent incidents from the local index (most recent first). Optionally filter by service.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
serviceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.14.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 carries the burden of behavioral disclosure. It mentions the local index source and sorting order, but does not mention read-only nature, potential rate limits, or return format. This is acceptable for a simple list tool but not comprehensive.

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 front-loaded sentence that communicates the core action, resource, ordering, and optional filter without any wasted words. It is highly concise and direct.

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 tool with two optional parameters and no output schema, the description covers the essential context: what is listed, from where, in what order, and the optional filter. Some missing details like limit semantics and return format are minor for this scope.

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 description coverage is 0%, so the description must compensate. It clarifies that 'service' is an optional filter, but does not explain 'limit' at all. The limit parameter is self-explanatory by name, but the description adds value only for service.

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 verb 'List', the resource 'recent incidents', and the scope 'from the local index' with ordering 'most recent first'. It inherently distinguishes from sibling tools that focus on pull requests, deployments, or Dora metrics.

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 phrase 'Optionally filter by service' gives some context for use, but there is no explicit guidance about when to choose this tool over alternatives like searchIndex or other getRecent tools. The usage is implied rather than clearly delineated.

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