Skip to main content
Glama
Sign In
Rivian MCP

Rivian MCP

by zentered-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rivian_get_ota_status

Read-only

Check the first Rivian vehicle's installed software version, OTA update status, and any available update details, including version and release notes link. Use it to see if an update is waiting.

Instructions

Get the installed software version, the update status reported by the vehicle (for example idle) and any available update with its version and release notes link. Use it to check whether an update is waiting. For the full account and vehicle list use rivian_get_user_info. Returns readable text; shows "up to date" when no update is available. Reads the first vehicle on the account. Requires a signed-in Rivian session and returns an error without one. Read-only: sends no command to the vehicle.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.3
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed3 schema fields changedv1.5.4
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / vehicle_id
      Removed value: -{
-  "description": "Vehicle ID from your account info",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "vehicle_id"
-]
  3. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the authentication prerequisite ('Requires a signed-in Rivian session and returns an error without one'), the scope limitation ('Reads the first vehicle on the account'), the side-effect profile ('sends no command to the vehicle'), and the return format including the 'up to date' sentinel. This is exactly the context annotations cannot carry.

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?

The core capability is front-loaded in the first sentence, followed by usage, alternative routing, return format, auth requirement, and read-only confirmation. Every sentence carries distinct information, though the description is on the long side for a no-argument read tool.

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?

With no output schema, the description still documents what comes back (readable text, 'up to date' when nothing is pending), the auth failure mode, and the single-vehicle scope. An agent has everything needed to call and interpret it.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to compensate for; baseline 4 applies. The description correctly does not invent parameter details.

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 names a specific verb+resource (installed software version, update status, available update) and scopes it precisely, noting it reads the first vehicle on the account. It explicitly distinguishes itself from the sibling rivian_get_user_info, which handles the full account/vehicle list.

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

Usage Guidelines4/5

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

'Use it to check whether an update is waiting' states the triggering condition clearly, and 'For the full account and vehicle list use rivian_get_user_info' names the alternative with the condition that selects it. There is no explicit when-not guidance, but the routing is unambiguous.

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