Skip to main content
Glama
Sign In
Rivian MCP

Rivian MCP

by zentered-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rivian_get_vehicle_state

Read-only

Read the current state of your Rivian, including battery, range, doors, windows, tires, location, climate, software, and security, without sending commands.

Instructions

Get the live vehicle state as readable text: battery level and range, doors, windows, tires, location, climate, seat heating and ventilation, steering wheel heat, software versions, and security and trailer status. Use it for how the vehicle is right now. For an active charge use rivian_get_charging_session; for past charges use rivian_get_charging_history; for updates use rivian_get_ota_status. Distances follow the unit set in the vehicle. 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
propertiesNoNames of the vehicle state properties to read, for example "batteryLevel" or "doorFrontLeftLocked". Omit or pass an empty array for the full report. An unknown name makes the Rivian API reject the request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.1
    • changedInput schema / properties / properties / description
      Previous value: -"Specific properties to check. Leave empty for a full status report."New value: +"Names of the vehicle state properties to read, for example \"batteryLevel\" or \"doorFrontLeftLocked\". Omit or pass an empty array for the full report. An unknown name makes the Rivian API reject the request."
  2. Changed2 schema fields changedv1.9.3
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Changed2 schema fields changedv1.5.4
    • removedInput schema / properties / vehicle_id
      Removed value: -{
-  "description": "Vehicle ID from your account info",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "vehicle_id"
-]
  4. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the auth requirement ('Requires a signed-in Rivian session and returns an error without one'), the account-scoping behavior ('Reads the first vehicle on the account'), the unit convention ('Distances follow the unit set in the vehicle'), and the side-effect profile ('sends no command to the vehicle'). These are the operational facts an agent needs before calling.

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-loads the resource and its contents, then moves to routing rules, then prerequisites and safety. Every sentence carries distinct information (contents, alternative routing, units, auth, read-only) with no filler.

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 compensates by enumerating the returned state categories, and it covers the auth prerequisite, account scoping, unit conventions, and the read-only guarantee. An agent has everything needed to call this correctly and interpret the result.

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%: the single 'properties' parameter already documents accepted names, the omit/empty-array behavior for a full report, and the failure mode for unknown names. The description adds nothing further about the parameter, so the baseline 3 for fully-documented schemas 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 and resource ('Get the live vehicle state as readable text') and enumerates the exact contents returned (battery, doors, windows, tires, location, climate, software versions, security/trailer). It clearly distinguishes itself from the charging and OTA siblings by naming them explicitly.

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?

Gives an explicit when-to-use rule ('Use it for how the vehicle is right now') and routes three adjacent cases to named alternatives: rivian_get_charging_session for active charge, rivian_get_charging_history for past charges, and rivian_get_ota_status for updates. Nothing is left to inference.

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