Skip to main content
Glama
Sign In
crashwebsite-mcp

crashwebsite-mcp

Official
by PluginCrashReports
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_crash_log

Retrieve full crash details and symbolicated stack trace by providing the crash's numeric ID.

Instructions

Get the full details and symbolicated stack trace (crashlog) for a single crash by its numeric id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_crash_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCrash id, as returned by the list/search tools.
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.7/5.0
Behavior3/5

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

No annotations exist, so description carries burden. It discloses output type (full details, stack trace) but no side effects, permissions, or limitations. Adequate for a simple read 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?

Single, direct sentence with no wasted words. Front-loaded with purpose.

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?

No output schema, and description lacks details on output fields. For a crash log retrieval tool, more completeness on returned data would be beneficial.

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 coverage is 100%, so schema already documents parameters. Description adds no extra meaning beyond confirming 'numeric id'.

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 retrieves full details and symbolicated stack trace for a single crash by numeric id, distinguishing it from list tools that return multiple crashes.

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 implies need for a numeric id but does not explicitly state when to use vs alternatives like get_crash_stats or list_recent_crashes. Lacks exclusions or comparisons.

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