Skip to main content
Glama
Sign In
Rivian MCP

Rivian MCP

by zentered-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rivian_get_charging_session

Read-only

Retrieve live Rivian charging session details: battery level, power, energy added, current, elapsed and remaining time, cost, charger location; if none active, show vehicle charging state.

Instructions

Get the charge happening now: battery level, power in kW, energy added in kWh, current in A, time elapsed and remaining, cost so far or free, whether it is a Rivian charger, and the charger location. When no live session exists, it reports the vehicle charging state instead. For finished sessions use rivian_get_charging_history; for planned charging use rivian_get_charging_schedule. Returns readable text. 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.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses an auth prerequisite and the failure mode ('Requires a signed-in Rivian session and returns an error without one'), an account-scoping quirk ('reads the first vehicle on the account'), a graceful degradation path (reports vehicle charging state when no session exists), and the return shape (readable text). These are operationally relevant facts not present in the annotations.

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 first sentence front-loads the core purpose and field inventory; routing guidance and preconditions follow in a logical order. It is dense and slightly list-heavy, and 'Returns readable text' is low-value filler, but no sentence is redundant.

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 carries the return-value burden and does so by enumerating the fields and stating the format is readable text. It also covers auth, account scoping, and the no-live-session case, so an agent has everything needed to call it and interpret results.

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 per the baseline this scores 4. The description's field list describes outputs rather than inputs, which is appropriate here.

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?

Names a specific verb and resource ('get the charge happening now') and enumerates the exact fields returned (battery level, kW, kWh, current, elapsed/remaining time, cost, charger identity/location). It explicitly differentiates itself from rivian_get_charging_history and rivian_get_charging_schedule by naming them as the tools for finished and planned sessions.

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 explicit routing rules: use this for a live session, rivian_get_charging_history for finished sessions, rivian_get_charging_schedule for planned charging. It also states the fallback behavior when no live session exists, so the agent knows there is no error case to route around.

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