Skip to main content
Glama
Sign In
Rivian MCP

Rivian MCP

by zentered-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rivian_get_charging_history

Read-only

List completed Rivian charging sessions, newest first, with date, time, duration, energy, cost, city, network, and charger type for every vehicle on the account.

Instructions

List past charging sessions, newest first. Each row has date, start and end time, duration, energy in kWh, cost or free, city, charging network and charger type (home, public or other). Use it for completed sessions. For a charge in progress use rivian_get_charging_session. Returns readable text. Includes charging sessions from every 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
limitNoHow many of the newest sessions to return, for example 10. Whole number of 1 or more. Defaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.1
    • changedInput schema / properties / limit / description
      Previous value: -"Number of newest sessions to show. Defaults to 25."New value: +"How many of the newest sessions to return, for example 10. Whole number of 1 or more. Defaults to 25."
  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"
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Number of newest sessions to show. Defaults to 25.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
  3. Addedv1.5.4

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint it adds real behavioral context: a signed-in Rivian session is required and an error is returned otherwise, sessions from every vehicle on the account are aggregated, and output is readable text. The read-only restatement mildly duplicates the annotation, but the auth, scope, and return-format disclosures are substantive additions.

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-loaded with the resource and ordering, then progressively adds row contents, usage routing, scope, and prerequisites. Sentences are dense and every one carries information; 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 returned fields (date, times, duration, kWh, cost/free, city, network, charger type). Auth requirements and account-wide scope are covered, so an agent has everything needed to invoke it correctly.

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%, and the single 'limit' parameter is fully documented in the schema (meaning, example, default of 25). The description adds nothing about the parameter, so the baseline 3 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?

The first sentence gives a specific verb and resource ('List past charging sessions, newest first') and the second enumerates exactly what each row contains. It explicitly distinguishes itself from the sibling tool rivian_get_charging_session, so an agent can route without opening a schema.

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?

It states when to use it ('Use it for completed sessions') and names the exact alternative for the excluded case ('For a charge in progress use rivian_get_charging_session'). Both the selection condition and the sibling routing are explicit.

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