Skip to main content
Glama

rivian_get_charging_schedule

Retrieve your Rivian's charging schedule to see scheduled charging times and days.

Instructions

See your charging schedule — what times and days your vehicle is set to charge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • mcp-server.js:206-219 (registration)
    Tool registration for 'rivian_get_charging_schedule' on the MCP server with description and empty schema.
    server.tool(
      'rivian_get_charging_schedule',
      'See your charging schedule — what times and days your vehicle is set to charge.',
      {},
      async () => {
        try {
          requireAuth()
          const vehicleId = await resolveVehicleId()
          return text(format.formatChargingSchedule(await rivian.getChargingSchedule(vehicleId)))
        } catch (err) {
          return text(err.message)
        }
      },
    )
  • Handler function: calls requireAuth(), resolves vehicle ID, fetches charging schedule via rivian.getChargingSchedule(), and formats the output via format.formatChargingSchedule().
    async () => {
      try {
        requireAuth()
        const vehicleId = await resolveVehicleId()
        return text(format.formatChargingSchedule(await rivian.getChargingSchedule(vehicleId)))
      } catch (err) {
        return text(err.message)
      }
    },
  • Input schema is an empty object '{}', so this tool takes no parameters.
    {},
  • API helper: getChargingSchedule() sends a GraphQL query 'GetChargingSchedule' to the Rivian API to fetch charging schedule data (startTime, duration, location, amperage, enabled, weekDays).
    export async function getChargingSchedule(vehicleId) {
      const body = {
        operationName: 'GetChargingSchedule',
        query: `query GetChargingSchedule($vehicleId: String!) {
      getVehicle(id: $vehicleId) {
        chargingSchedules {
          startTime
          duration
          location { latitude longitude }
          amperage
          enabled
          weekDays
        }
      }
    }`,
        variables: { vehicleId },
      }
    
      return (await gql(GRAPHQL_GATEWAY, body, authHeaders())).getVehicle
    }
  • Format helper: formatChargingSchedule() formats the raw charging schedule data into human-readable text showing time ranges, amperage, days, and location.
    export function formatChargingSchedule(data) {
      const schedules = data?.chargingSchedules
      if (!schedules?.length) return c.dim('No charging schedules configured.')
    
      const lines = [section('Charging Schedules'), '']
    
      for (const s of schedules) {
        const startHour = Math.floor(s.startTime / 60)
        const startMin = s.startTime % 60
        const endMinutes = s.startTime + s.duration
        const endHour = Math.floor(endMinutes / 60) % 24
        const endMin = endMinutes % 60
    
        const fmt = (h, m) => {
          const period = h >= 12 ? 'PM' : 'AM'
          const hour12 = h % 12 || 12
          return `${hour12}:${String(m).padStart(2, '0')} ${period}`
        }
    
        const enabled = s.enabled ? c.green('●') : c.red('●')
        lines.push(
          `  ${enabled} ${c.bold(`${fmt(startHour, startMin)} – ${fmt(endHour, endMin)}`)} ${c.dim(`(${s.duration / 60}h)`)}`,
        )
        lines.push(kv('Amperage', s.amperage, 'A'))
        if (s.weekDays?.length) lines.push(kv('Days', s.weekDays.join(', ')))
        if (s.location) lines.push(kv('Location', `${s.location.latitude}, ${s.location.longitude}`))
        lines.push('')
      }
    
      return lines
        .filter((l) => l !== null)
        .join('\n')
        .trim()
    }
Behavior3/5

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

No annotations provided, so description must carry the burden. It implies a read-only operation but does not explicitly state no side effects or disclose any behavioral traits like authentication requirements or rate limits. Adequate but minimal.

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, clear sentence with no wasted words. Front-loaded with the core action ('See your charging schedule'). Extremely efficient.

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 zero parameters and no output schema, the description is minimal but functional. Lacks usage guidelines and behavioral disclosure, which reduces completeness for a tool with siblings.

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?

No parameters exist, so schema coverage is 100%. Baseline for zero parameters is 4, and description adds no param info, which is appropriate since none are needed.

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's purpose: viewing the charging schedule. Uses a specific verb ('see') and resource ('charging schedule'), and distinguishes from siblings like charging history and session tools.

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?

No guidance on when to use this tool versus alternatives (e.g., rivian_get_charging_history or rivian_get_charging_session). The description does not provide context for selection.

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