Skip to main content
Glama

rivian_get_ota_status

Check your Rivian vehicle's current software version and available OTA updates using the vehicle ID from your account.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vehicle_idYesVehicle ID from your account info

Implementation Reference

  • mcp-server.js:489-503 (registration)
    Tool registration with schema (vehicle_id parameter) and handler that calls rivian.getOTAUpdateDetails and formats the output
    server.tool(
      'rivian_get_ota_status',
      "Check for software updates — what version you're running and whether a new one is available.",
      {
        vehicle_id: z.string().describe('Vehicle ID from your account info'),
      },
      async ({ vehicle_id }) => {
        try {
          requireAuth();
          return text(formatOTAStatus(await rivian.getOTAUpdateDetails(vehicle_id)));
        } catch (err) {
          return text(err.message);
        }
      },
    );
  • Core implementation that executes a GraphQL query to Rivian's API to fetch current and available OTA update details for a vehicle
    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 }
      }
    }`,
        variables: { vehicleId },
      };
    
      return (await gql(GRAPHQL_GATEWAY, body, authHeaders())).getVehicle;
    }
  • Helper function that formats the OTA status data into human-readable text showing current version and available updates
    function formatOTAStatus(ota) {
      const lines = [];
    
      if (ota.currentOTAUpdateDetails) {
        lines.push(`Current software: v${ota.currentOTAUpdateDetails.version}`);
      } else {
        lines.push('Current software: unknown');
      }
    
      if (ota.availableOTAUpdateDetails) {
        lines.push(`Update available: v${ota.availableOTAUpdateDetails.version}`);
        if (ota.availableOTAUpdateDetails.url) {
          lines.push(`Release notes: ${ota.availableOTAUpdateDetails.url}`);
        }
      } else {
        lines.push('No update available — software is up to date.');
      }
    
      return lines.join('\n');
    }
  • Helper function that constructs authentication headers required for authenticated API calls including the OTA status query
    function authHeaders() {
      return { 'A-Sess': appSessionToken, 'U-Sess': userSessionToken };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Check' implies a read-only operation, it doesn't explicitly state whether this requires authentication, has rate limits, returns real-time or cached data, or what format the response takes. For a tool that likely requires authentication (given the vehicle_id parameter), this is a significant 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?

The description is perfectly concise - a single sentence that efficiently communicates the core functionality. Every word earns its place, and the structure is front-loaded with the main purpose followed by specific details about what information is retrieved.

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?

Given the tool's moderate complexity (vehicle software status check), no annotations, no output schema, and 100% schema coverage, the description is minimally adequate. It explains what the tool does but lacks important context about authentication requirements, response format, and how this differs from sibling tools. The description meets basic requirements but leaves significant gaps for an agent to operate effectively.

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% with the single parameter 'vehicle_id' well-documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, but with complete schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Check for software updates' with specific details about checking current version and update availability. It uses a specific verb ('Check') and resource ('software updates'), though it doesn't explicitly differentiate from sibling tools like rivian_get_vehicle_state which might also provide version information.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like authentication status), when this tool is appropriate versus other vehicle information tools, or any exclusions. The agent must infer usage context from the tool name alone.

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