Skip to main content
Glama
Sign In
podium-mcp

podium-mcp

by hoainho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

crash_list

Retrieve crash reports from macOS DiagnosticReports, filtered by process name or time, including simulator crashes when UDID is provided.

Instructions

Lists crash reports (.ips/.crash) from ~/Library/Logs/DiagnosticReports — plus the simulator's own container DiagnosticReports when udid is given — sorted newest first. Filter by processName (case-insensitive substring) and/or sinceHours.

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

Input Schema

NameRequiredDescriptionDefault
processNameNoCase-insensitive substring to filter by process name
sinceHoursNoOnly include crashes from the last N hours
udidNoSimulator UDID — also scans that sim's container DiagnosticReports

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses directories scanned, sorting order, filtering behavior. No annotations provided, but description fairly covers behavioral aspects for a list operation.

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?

Two efficient sentences: first covers main function, second adds key filtering details. No waste.

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?

Describes inputs and behavior adequately for a list tool. No output schema, but return format is implicit. Incomplete only in not describing output structure, but acceptable given sibling crash_get.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds context about udid expanding search to simulator container and sorting order, beyond schema definitions.

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?

Description clearly states it lists crash reports from a specific directory, sorted newest first, with filtering. Distinguishes from sibling crash_get by focusing on listing.

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

Usage Guidelines4/5

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

Provides clear context for when to use (to browse crashes) and filtering options, but no explicit mention of when not to use or alternatives beyond sibling tool names.

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