Skip to main content
Glama
zentered-studios

Rivian MCP

by zentered-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rivian_get_ota_status

Read-only

Check your Rivian's current OTA software version and see if an update is available.

Instructions

Get the installed software version and any available update.

Input Schema

TableJSON 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-state profile is covered. The description adds that the result covers both the installed version and available updates, but says nothing about freshness, caching, or whether the vehicle must be online.

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?

A single front-loaded sentence with no filler; every word contributes to identifying the resource and the returned content.

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

Completeness4/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, naming the returned content (installed version + available update) is what an agent most needs. Minor gaps remain around staleness/refresh behavior and account prerequisites, but nothing essential is missing.

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 per the rubric the baseline is 4. There is no parameter semantics to document and none are misrepresented.

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?

States a concrete verb ('Get') and a specific resource pair (installed software version and available OTA update), which is clearly distinct from sibling read tools like get_vehicle_state or get_charging_schedule. It does not explicitly name or contrast with any sibling, keeping it short of a 5.

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 when-to-use, when-not-to-use, or alternative-tool guidance is given. The only usage signal is implicit in the resource name, which matches the 'no guidance' band.

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