Skip to main content
Glama
Sign In
Rivian MCP

Rivian MCP

by zentered-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rivian_get_drivers_and_keys

Read-only

List invited drivers, enrolled phone keys, and key fobs to audit who can access or drive the first vehicle. Read-only; requires a signed-in Rivian session.

Instructions

List who and what can open and drive the vehicle: invited drivers, enrolled phone keys and key fobs. Use it to audit access to the vehicle. It does not add or revoke access. For account and vehicle details use rivian_get_user_info. 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?

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the auth prerequisite ('Requires a signed-in Rivian session and returns an error without one'), the implicit scoping behavior ('Reads the first vehicle on the account'), and the return format ('Returns readable text'). These are exactly the traits an agent cannot derive from the structured fields.

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?

Front-loaded with the core purpose and kept to short, scannable sentences with no filler. The closing 'Read-only: sends no command to the vehicle' partially restates the readOnlyHint annotation, a minor redundancy in an otherwise tight definition.

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?

For a zero-parameter read tool with no output schema, the description covers everything needed: what it returns, the format, the auth requirement, the error behavior, and the vehicle scope. An agent has no remaining questions before invoking 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 the baseline is 4. The description correctly explains why no selector exists by noting it reads the first vehicle on the account, which compensates for the absent vehicle-selection parameter.

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 ('List who and what can open and drive the vehicle') and enumerates the concrete items returned: invited drivers, enrolled phone keys, key fobs. It also explicitly differentiates itself from the sibling rivian_get_user_info, so an agent can route correctly without opening either 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?

Gives explicit when-to-use ('Use it to audit access to the vehicle'), an explicit boundary ('It does not add or revoke access'), and names the alternative tool for a related need ('For account and vehicle details use rivian_get_user_info'). Nothing about selection 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