Skip to main content
Glama
Sign In
@loggydev/mcp-server

@loggydev/mcp-server

by loggy-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_alerts

Retrieve a list of recent alerts from Loggy, with an optional limit parameter to control the number returned.

Instructions

List recent alerts

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of alerts to return (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. It only says 'List recent alerts', offering no information on sorting, pagination, default limit (if any), or whether it's read-only. The agent cannot infer side effects or constraints beyond the input schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (2 words), but conciseness is not optimal if it sacrifices clarity. It is front-loaded but lacks detail expected for a tool. Every word earns its place, but it is under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 fails to explain what 'recent' means, the ordering of results, or default behavior. The agent lacks enough context to use the tool confidently.

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% (limit parameter is described). The description adds no extra meaning beyond the schema. Since coverage is high, baseline 3 is appropriate; the description does not degrade or enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List recent alerts' clearly states the verb (list) and resource (alerts). It is not a tautology and distinguishes from sibling tools like 'list_heartbeats' by resource type. However, 'recent' is ambiguous—lacking a definition of time window—so it's not perfectly specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not indicate when to use this tool over alternatives (e.g., for non-recent or filtered alerts, or compared to other list tools). No exclusions or context are given.

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