Skip to main content
Glama

rivian_get_ota_status

Check your Rivian's current software version and detect if a new update is available.

Instructions

Check for software updates — what version you're running and whether a new one is available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registration of the 'rivian_get_ota_status' tool on the MCP server. The handler calls requireAuth(), resolves the vehicle ID, then calls rivian.getOTAUpdateDetails(vehicleId) and formats the result via format.formatOTAStatus().
    server.tool(
      'rivian_get_ota_status',
      "Check for software updates — what version you're running and whether a new one is available.",
      {},
      async () => {
        try {
          requireAuth()
          const vehicleId = await resolveVehicleId()
          return text(format.formatOTAStatus(await rivian.getOTAUpdateDetails(vehicleId)))
        } catch (err) {
          return text(err.message)
        }
      },
  • The GraphQL query that fetches OTA update details for a vehicle: availableOTAUpdateDetails, currentOTAUpdateDetails, and vehicleState.otaStatus.
    export async function getOTAUpdateDetails(vehicleId) {
      const body = {
        operationName: 'getOTAUpdateDetails',
        query: `query getOTAUpdateDetails($vehicleId: String!) {
      getVehicle(id: $vehicleId) {
        availableOTAUpdateDetails { url version locale }
        currentOTAUpdateDetails { url version locale }
        vehicleState {
          otaStatus { value timeStamp }
        }
      }
    }`,
        variables: { vehicleId },
      }
    
      return (await gql(GRAPHQL_GATEWAY, body, authHeaders())).getVehicle
    }
  • Formats the OTA status data into a human-readable string showing current version, update status, and whether a new update is available.
    export function formatOTAStatus(ota) {
      const lines = []
    
      lines.push(section('Software Update'))
      lines.push('')
    
      if (ota.currentOTAUpdateDetails) {
        lines.push(kv('Current', `v${ota.currentOTAUpdateDetails.version}`))
      } else {
        lines.push(kv('Current', c.dim('unknown')))
      }
    
      const otaStatus = ota.vehicleState?.otaStatus?.value
      if (otaStatus) {
        const statusColor = otaStatus.toLowerCase() === 'idle' ? c.green : c.yellow
        lines.push(kv('Status', statusColor(otaStatus)))
      }
    
      if (ota.availableOTAUpdateDetails) {
        lines.push(kv('Update available', c.yellow(`v${ota.availableOTAUpdateDetails.version}`)))
        if (ota.availableOTAUpdateDetails.url) {
          lines.push(kv('Release notes', ota.availableOTAUpdateDetails.url))
        }
      } else if (otaStatus && otaStatus.toLowerCase() !== 'idle') {
        lines.push('')
        lines.push(`  ${c.yellow('⏳')} Flagged for update — details pending.`)
      } else {
        lines.push('')
        lines.push(`  ${c.green('✓')} Software is up to date.`)
      }
    
      return lines.filter((l) => l !== null).join('\n')
    }
  • mcp-server.js:162-175 (registration)
    Tool registration via server.tool() call with the name 'rivian_get_ota_status'. Also serves as the handler in this file since the implementation is inline.
    server.tool(
      'rivian_get_ota_status',
      "Check for software updates — what version you're running and whether a new one is available.",
      {},
      async () => {
        try {
          requireAuth()
          const vehicleId = await resolveVehicleId()
          return text(format.formatOTAStatus(await rivian.getOTAUpdateDetails(vehicleId)))
        } catch (err) {
          return text(err.message)
        }
      },
    )
Behavior2/5

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

No annotations provided. Description indicates a non-destructive 'check' operation, but does not mention authentication requirements or other behavioral traits (e.g., rate limits). For a tool requiring login (sibling rivian_login exists), this is a gap.

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?

Single sentence, front-loaded with primary action, no extraneous words. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists. Description hints at return content (version, update availability) but does not specify structure or additional fields. Adequate for a simple tool, but could be more complete.

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?

Input schema has zero parameters, so baseline is 4. Description adds no param info, but none needed since schema coverage is 100%.

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?

Description clearly states the tool checks for software updates, reports current version, and indicates availability of a new one. Distinct from sibling tools (charging, keys, etc.), which are about different vehicle functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives guidance. Given the tool is a simple status check, the usage context is implied, but no exclusions or sibling comparisons are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PatrickHeneise/rivian-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server