Skip to main content
Glama
Sign In
crashwebsite-mcp

crashwebsite-mcp

Official
by PluginCrashReports
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_crash_stats

Get aggregate crash statistics for a plugin: total, last 7/30 days, unique functions, and breakdowns by version and platform.

Instructions

Get aggregate crash statistics for a plugin: total, last 7/30 days, unique functions, and breakdowns by version and platform.

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

Input Schema

NameRequiredDescriptionDefault
pluginNoWhich plugin to query: id, plugin code, or name. Omit if you have only one; otherwise required (see list_plugins).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description must disclose behavioral traits. It states 'Get' implying read-only, but does not explicitly confirm no side effects, rate limits, or data freshness. More transparency would improve this score.

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 sentence that efficiently lists the key return elements with no redundancy or unnecessary words.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description lists the types of statistics but does not specify the output structure or format. Additional detail on the breakdowns (e.g., nested objects or separate fields) would improve completeness.

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% and provides clear guidance on the 'plugin' parameter. The tool description adds no additional semantic meaning beyond what the schema already offers.

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 'Get aggregate crash statistics for a plugin' with specific verb and resource, and lists distinct statistics (total, last 7/30 days, unique functions, breakdowns), which distinguishes it from sibling tools like get_crash_log or list_frequent_crashes.

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?

The description implies usage for aggregate stats and the input schema for 'plugin' provides guidance on when to provide it (omit if only one plugin, otherwise required with reference to list_plugins). However, no explicit when-not or alternatives to other crash-related tools are stated.

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