UberSync MCP Server

Safety Details

safety_details

Retrieve safety details for a specific ride using its ride ID. Verify safety information for any demo ride to ensure a secure trip experience.

Instructions

Return safety information for a demo ride.

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": {
      "rideId": "<rideId>"
    },
    "name": "safety_details"
  }
}

Input Schema

Name	Required	Description	Default
`rideId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must supply the behavioral context, but it only says 'Return,' which implies read-only without stating side effects, permissions, or output behavior. It gives no information about what safety details are included or what happens for invalid ride IDs.

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?

One sentence with no filler and the key operation is front-loaded. It is appropriately short, though it sacrifices informative content.

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

Completeness2/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 and no annotations, the description does not explain what safety information will be returned, how to use rideId, or what distinguishes this call from similar ride-information tools. The description is too minimal to fully support correct invocation.

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?

Schema description coverage is 0%, so the description carries the burden of explaining rideId, but it only mentions 'for a demo ride' without explicitly defining rideId as the identifier of the demo ride or describing its format and expected values. This adds minimal meaning beyond the schema's minLength constraint.

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?

Describes a specific verb ('Return') and resource ('safety information') for a ride, and 'safety' is not addressed by any sibling tool, so an agent can understand what it does. However, it does not explicitly differentiate itself from closely related ride-information siblings such as get_ride_details or get_trip_details.

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

Usage Guidelines2/5

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

No guidance is provided for when to choose this tool over the many ride-related siblings, such as get_ride_details or get_trip_details. 'For a demo ride' hints at a use case but does not explain when safety_details is appropriate or when it should be avoided.

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