Skip to main content
Glama
Sign In
bluelink-mcp

bluelink-mcp

by mattoddie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List vehicles

list_vehicles
Read-only

Retrieve all Hyundai, Kia, or Genesis vehicles linked to your Bluelink account, then use each vehicle to check status or send supported commands.

Instructions

List the vehicles on the account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_vehicles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 profile is covered. The description adds only 'on the account', a small scoping detail, and says nothing about pagination, account auth, or result ordering; with an output schema present, return details are excused, so a 3 is fair.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no filler or redundancy. It is efficiently sized for a simple list tool, though it is so terse that it forgoes any structural elaboration.

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?

With an output schema, full annotation coverage, and no parameters, the description is nearly sufficient, but it omits any relationship to the sibling tools that all consume vehicle identities. For an entry-point listing tool in a seven-tool family, that missing context is a real gap.

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 the baseline of 4 applies. There is no parameter information the description could usefully add beyond what the empty schema already conveys.

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 specific verb (List) and resource (vehicles) with scope ('on the account'), so an agent immediately knows this enumerates vehicles. However, it offers no explicit differentiation from sibling tools like get_vehicle_status or get_vehicle_location, leaving the agent to infer that this is the enumeration entry point.

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?

Usage is only implied: an agent can reasonably guess this is the discovery tool to run before the per-vehicle getters, but the description never says when to prefer it or how it relates to the six sibling getters. No exclusions or prerequisites are stated.

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