UberSync MCP Server

Emergency Help

emergency_help

Access safety procedures for emergencies during a ride. Provides clear step-by-step guidance without connecting to emergency services.

Instructions

Show safe emergency guidance. This demo does not contact emergency dispatch.

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

Input Schema

Name	Required	Description	Default
`rideId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly discloses the critical behavioral boundary: 'This demo does not contact emergency dispatch.' It also signals a read-only display action through 'Show safe emergency guidance.' This is meaningful transparency for a safety-related tool.

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 short sentences, no filler, with the key safety caveat placed prominently. Every word earns its place and the structure is easy to parse.

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 low-complexity tool with one optional parameter and no output schema, the description covers the core purpose and the most important safety boundary. However, it omits any explanation of rideId's role and does not situate the tool relative to safety_details, leaving some gaps for an agent deciding how to invoke it.

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

Parameters2/5

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

The schema has 0% description coverage for rideId, and the description does not mention the parameter at all. The agent cannot tell whether rideId is needed, optional context, or how it affects the guidance shown. The description fails to compensate for the missing schema documentation.

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?

The description uses a specific verb and resource: 'Show safe emergency guidance.' It clearly conveys the purpose, but it does not explicitly distinguish itself from the sibling tool 'safety_details,' so it lacks full sibling differentiation.

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 usage context by stating it is a demo and explicitly notes that it does not contact emergency dispatch. However, it provides no direct when-to-use guidance or alternatives, leaving the agent to infer when this tool is preferable to safety_details or contact_driver.

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