CityAlert

Submit incident report

submit_report

File a manual geolocated incident report (same as POST /api/reports). Reports are moderated before they appear publicly. Errors: 'report submission disabled' if the caller is blocked; 'rate limited' past 20 reports/hour via MCP.

Input Schema

Name	Required	Description
`lat`	Yes	Latitude, -90 to 90
`lon`	Yes	Longitude, -180 to 180
`title`	Yes	Short headline, 1–200 chars
`category`	No	Incident category (default 'report')
`severity`	No	low \| medium \| high \| critical (default 'medium')
`description`	No	Details, up to 2000 chars

Output Schema

Name	Required	Description	Default
`report`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 10, 2026

addedInput schema / properties / category / description

Added value: +"Incident category (default 'report')"

addedInput schema / properties / description / description
```
Added value: +"Details, up to 2000 chars"
```
addedInput schema / properties / lat / description
```
Added value: +"Latitude, -90 to 90"
```
addedInput schema / properties / lon / description
```
Added value: +"Longitude, -180 to 180"
```

addedInput schema / properties / severity / description

Added value: +"low | medium | high | critical (default 'medium')"

addedInput schema / properties / title / description
```
Added value: +"Short headline, 1–200 chars"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "report": {
+      "additionalProperties": false,
+      "properties": {
+        "approximate": {
+          "type": "boolean"
+        },
+        "category": {
+          "type": "string"
+        },
+        "confirms": {
+          "type": "number"
+        },
+        "count": {
+          "type": "number"
+        },
+        "description": {
+          "type": "string"
+        },
+        "flags": {
+          "type": "number"
+        },
+        "group": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "lat": {
+          "type": "number"
+        },
+        "lon": {
+          "type": "number"
+        },
+        "nhood": {
+          "type": "string"
+        },
+        "region": {
+          "type": "string"
+        },
+        "reporter": {
+          "additionalProperties": false,
+          "properties": {
+            "confirmed": {
+              "type": "number"
+            },
+            "handle": {
+              "type": "string"
+            },
+            "reports": {
+              "type": "number"
+            },
+            "role": {
+              "anyOf": [
+                {
+                  "enum": [
+                    "curator",
+                    "moderator"
+                  ],
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "required": [
+            "handle",
+            "role",
+            "reports",
+            "confirmed"
+          ],
+          "type": "object"
+        },
+        "resolves": {
+          "type": "number"
+        },
+        "severity": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        },
+        "sources": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "status": {
+          "enum": [
+            "pending",
+            "active",
+            "resolved",
+            "hidden"
+          ],
+          "type": "string"
+        },
+        "time": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "source",
+        "category",
+        "type",
+        "title",
+        "lat",
+        "lon",
+        "time",
+        "severity"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "report"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "crime",
-  "fire",
-  "disaster",
-  "weather",
-  "unrest",
-  "health",
-  "infra",
-  "report"
-]New value: +[
+  "crime",
+  "fire",
+  "disaster",
+  "weather",
+  "unrest",
+  "health",
+  "infra",
+  "alert",
+  "report"
+]

First observedSep 19, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations cover the write/safety profile (readOnlyHint=false, destructiveHint=false), and the description adds substantial non-structured context: moderation before public appearance, the 'report submission disabled' blocked-caller error, and the 20 reports/hour MCP rate limit. This is exactly the kind of extra behavioral disclosure wanted.

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?

Three tight, front-loaded clauses with no filler. Slightly dense but every sentence earns its place.

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?

An output schema exists so return values need not be explained, and the behavioral notes cover moderation and failure modes. Only missing piece is explicit sibling differentiation/usage guidance.

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% with bounds, enums, and defaults fully documented in the schema. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (file/submit) and resource (manual geolocated incident report), and parenthetically ties it to the POST /api/reports endpoint. It does not explicitly distinguish itself from sibling read tools like get_incidents, though the write framing is clear.

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?

Implied usage (file an incident report) but no explicit when-to-use vs alternatives or when-not-to-use conditions. The moderation and error notes give context but not selection guidance.

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

All CityAlert tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?