Skip to main content
Glama
ProjectMakersDE

horizOn MCP Server

Official
by ProjectMakersDE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Crash Report

horizon_create_crash_report

Send a crash, non-fatal exception, or ANR report with device details to horizOn Crash Reporting so issues group by fingerprint.

Instructions

Submits one crash (CRASH), caught exception (NON_FATAL) or freeze (ANR) with device data to horizOn Crash Reporting, grouped by fingerprint. Use when: the game crashed (send on next start) or caught an exception worth tracking. Not for: technical events without a crash (use horizon_create_log) and messages written by players (use horizon_submit_feedback). Requires: a sessionId registered with horizon_create_crash_session for this app run; userId is optional. Side effects: adds one report per call (a repeat adds a duplicate) and marks the session as crashed. Reports with the same fingerprint form one group; a group marked resolved becomes REGRESSED when a newer app version crashes again. Returns: {id, groupId, createdAt}; groupId identifies the crash group in the dashboard. Errors: 400 when a required field is missing or too long: fix it and resend. Needs HORIZON_API_KEY. Every failure returns an error result (isError) with the HTTP status and body: a 401 that horizon_test_connection also returns means HORIZON_API_KEY is wrong, 429 means the account's per-minute rate limit was reached (wait a minute, then retry).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osYesOS details (e.g. 'Android 14', 'iOS 17.2')
typeYesCrash type: CRASH (fatal), NON_FATAL (exception), or ANR (Application Not Responding)
userIdNoPlayer user ID (UUID) from horizon_signup_* or horizon_signin_*, if a player is signed in
messageYesError or exception message (1 to 5000 characters)
platformYesPlatform (e.g. 'Android', 'iOS', 'Windows')
sessionIdYesThe sessionId registered with horizon_create_crash_session for this app run (1 to 100 characters)
appVersionYesApp version (e.g. '1.2.3')
customKeysNoString key to string value metadata such as level or build flavor (max 10 entries)
sdkVersionYeshorizOn SDK version, for example '1.8.2' (1 to 50 characters)
stackTraceNoFull stack trace (max 20000 characters)
breadcrumbsNoRecent events before the crash, oldest first (max 50)
deviceModelYesDevice model (e.g. 'Pixel 8', 'iPhone 15')
fingerprintYesGrouping key: reports with the same fingerprint form one crash group, for example a hash of exception type and top stack frame (1 to 128 characters)
deviceMemoryMbNoDevice RAM in MB, for example 8192

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.6.0
    • changedInput schema / properties / breadcrumbs / description
      Previous value: -"Activity trail before the crash (max 50 items)"New value: +"Recent events before the crash, oldest first (max 50)"
    • changedInput schema / properties / breadcrumbs / items / properties / timestamp / description
      Previous value: -"When the event occurred"New value: +"When the event occurred, ISO 8601 (for example 2026-09-29T14:03:12Z)"
    • changedInput schema / properties / customKeys / description
      Previous value: -"Key-value metadata (max 10 entries)"New value: +"String key to string value metadata such as level or build flavor (max 10 entries)"
    • changedInput schema / properties / deviceMemoryMb / description
      Previous value: -"Device RAM in MB"New value: +"Device RAM in MB, for example 8192"
    • changedInput schema / properties / fingerprint / description
      Previous value: -"Grouping key — crashes with the same fingerprint are grouped together (1-128 characters)"New value: +"Grouping key: reports with the same fingerprint form one crash group, for example a hash of exception type and top stack frame (1 to 128 characters)"
    • changedInput schema / properties / message / description
      Previous value: -"Error message (1-5000 characters)"New value: +"Error or exception message (1 to 5000 characters)"
    • changedInput schema / properties / sdkVersion / description
      Previous value: -"horizOn SDK version"New value: +"horizOn SDK version, for example '1.8.2' (1 to 50 characters)"
    • changedInput schema / properties / sessionId / description
      Previous value: -"Session ID from horizon_create_crash_session"New value: +"The sessionId registered with horizon_create_crash_session for this app run (1 to 100 characters)"
    • changedInput schema / properties / userId / description
      Previous value: -"User ID (UUID) who experienced the crash"New value: +"Player user ID (UUID) from horizon_signup_* or horizon_signin_*, if a player is signed in"
  2. First observedv1.5.4

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false): it discloses that each call adds a report and repeats create duplicates, that the session is marked crashed, that same-fingerprint reports form a group, and that resolved groups become REGRESSED on a newer version. It also documents auth (HORIZON_API_KEY), error behavior (400/401/429) and the isError contract.

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?

Front-loaded with the core action, then cleanly segmented into Use when / Not for / Requires / Side effects / Returns / Errors. Despite its length, every section carries distinct information, so nothing is wasted.

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

Completeness5/5

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

For a 14-parameter, 9-required mutation with a nested breadcrumbs array and no output schema, the description supplies return shape ({id, groupId, createdAt}), grouping semantics, auth requirements, and error handling. An agent has everything needed to invoke it correctly.

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 already documents all 14 parameters including fingerprint grouping and sessionId provenance. The description adds only marginal meaning (userId optional, sessionId must come from horizon_create_crash_session), so the baseline 3 applies.

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?

States a specific verb (Submits) and resource (a CRASH/NON_FATAL/ANR report with device data) plus the grouping model by fingerprint. It explicitly distinguishes itself from horizon_create_log and horizon_submit_feedback, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Provides explicit 'Use when', 'Not for', and 'Requires' sections. It names the two alternatives (horizon_create_log, horizon_submit_feedback) with the conditions that select them, and specifies the sessionId prerequisite from horizon_create_crash_session.

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