Skip to main content
Glama
Sign In
Stellaris MCP

Stellaris MCP

by GDM-Pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

usage_anomalies

Identify Claude Code sessions that surpass health thresholds for cost, turns, tokens, or idle duration to manage usage anomalies.

Instructions

List Claude Code sessions that hit health thresholds: SES001 cost ≥$25, SES002 ≥200 turns, SES003 ≥5M tokens, SES004 idle 7+ days. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
periodNoTime period to check for anomalies (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.4.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses 'No API key required' and lists specific thresholds, but does not mention side effects, return format, or behavior when no anomalies exist.

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, well-structured sentence that front-loads the main purpose and then lists thresholds with no superfluous content.

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 list tool with one optional parameter and no output schema, the description adequately covers thresholds and auth requirements. However, it omits scope (e.g., current workspace or all workspaces) and handling of edge cases.

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 100% for the single parameter 'period', with enum values and description. The tool description adds no parameter info beyond the schema, meeting the baseline for parameter semantics.

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 lists Claude Code sessions hitting specific health thresholds, with explicit threshold definitions (SES001 cost ≥$25, etc.). It distinguishes itself from sibling tools by focusing on anomaly detection.

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 provides context but no explicit when-to-use or when-not-to-use guidance relative to siblings. It implies usage for finding anomalous sessions but does not reference alternative tools or exclusions.

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