Skip to main content
Glama
Sign In
Rivian MCP

Rivian MCP

by zentered-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rivian_submit_otp

Submit the Rivian verification code after rivian_login confirms one was sent to complete sign-in and save your session; errors if no pending login.

Instructions

Finish a Rivian sign-in with the verification code Rivian sent to your phone or email. Use it only after rivian_login reported that a code was sent; without a pending sign-in it returns an error and asks you to call rivian_login. On success it saves the session to ~/.rivian-mcp/session.json. Uses the RIVIAN_EMAIL set in the MCP server configuration. Returns a message saying you are signed in, or an error if Rivian rejects the code.

Input Schema

NameRequiredDescriptionDefault
otp_codeYesThe verification code exactly as Rivian sent it, as a string, for example "123456". Do not include spaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.1
    • changedInput schema / properties / otp_code / description
      Previous value: -"The verification code"New value: +"The verification code exactly as Rivian sent it, as a string, for example \"123456\". Do not include spaces."
  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. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true); the description goes further by disclosing a concrete side effect (session persisted to ~/.rivian-mcp/session.json), a configuration dependency (RIVIAN_EMAIL from server config), and both success and rejection return behavior.

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?

Four short sentences, front-loaded with the action and the sequencing constraint, followed by the side effect and return behavior. No filler and nothing repeated from the schema.

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 must describe returns, and it does ('a message saying you are signed in, or an error if Rivian rejects the code'). Combined with preconditions, auth source, and persistence, an agent has everything needed to call 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?

There is a single parameter with 100% schema description coverage, so the schema already defines format, type, and the no-spaces rule. The description adds only the faintly useful provenance detail that the code arrives by phone or email, which is the baseline-3 case.

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 ('Finish a Rivian sign-in with the verification code') and names the sibling tool it complements (rivian_login), so the agent can distinguish it from the eight other rivian_* tools immediately.

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 precondition ('Use it only after rivian_login reported that a code was sent') and states the failure path when that precondition is unmet ('it returns an error and asks you to call rivian_login'). That is a full when-to-use / what-happens-otherwise rule.

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