Skip to main content
Glama

List releases and their health

list_releases
Read-only

Releases from the app and the backend, newest first: crash-free sessions, users and adoption for the app, crash-free and error-free requests for the backend. Use it to tell whether a release made things worse. crashed_sessions counts crashes and bad exits; abnormal_sessions is the bad exits (no crash report, an AbnormalExit issue). release (version+build) is the name every tool takes.

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_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days (default 30)
limitNoRows (default 25)
cursorNonext_cursor from the last answer
sourceNoDefault all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive. The description adds useful behavioral context beyond that: it specifies result ordering (newest first), defines non-obvious fields like crashed_sessions and abnormal_sessions, and notes that `release` (version+build) is the common identifier across tools.

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?

The description is front-loaded with the core purpose and packs field definitions into two dense sentences without wasted words. It could be slightly better structured, but it is not verbose.

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?

Without an output schema, the description does the necessary work of explaining the returned health metrics and their meaning. It leaves pagination (cursor) to the schema, which is a minor gap but overall sufficient for correct invocation.

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%, so the schema fully documents all four parameters. The description does not add syntax or default details beyond the schema, which is acceptable at baseline 3.

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 clearly states the verb (list) and resource (releases), and enumerates the health metrics returned for app and backend. It does not explicitly contrast with siblings like compare_releases, so it stops short of a 5.

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?

It gives an implied use case ('Use it to tell whether a release made things worse') but offers no explicit when-not-to-use guidance or named alternatives, leaving the agent to infer when to choose compare_releases or another tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources