Skip to main content
Glama
Sign In
bluelink-mcp

bluelink-mcp

by mattoddie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get trips

get_trips
Read-only

Retrieve a vehicle's driving history for a specific day or month, showing trip details or daily trip counts. Available in supported regions such as Europe.

Instructions

Get driving history: trips for a day, or a month's summary with trip counts per day. Not every region supports this (Europe does).

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": "get_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD for that day's trips, or YYYY-MM for a month summary. Defaults to today.
vehicleNoVehicle name, VIN or ID. Optional if the account has one vehicle.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 the regional availability constraint, which is valuable context not in annotations, but doesn't describe pagination, rate limits, or output format.

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?

Two compact sentences front-load the core action and then the key constraint; no wasted words.

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?

Given a full output schema exists, return values needn't be explained. The tool is read-only with clear annotations. The regional caveat is important, but minor gaps like error behavior or result limits keep this from a 5.

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 coverage is 100% with detailed parameter descriptions, so the schema already documents the date formats and vehicle parameter fully. The description only repeats 'day or month summary' without adding format syntax or other meaning.

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?

States a specific verb and resource ('Get driving history: trips') and clearly delineates the two modes—day trips vs month summary—distinguishing it from siblings like get_vehicle_location or get_energy_usage.

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?

The regional support caveat ('Not every region supports this') is useful but there's no explicit guidance on when to use this vs alternatives like get_energy_usage; usage is implied by the purpose but not spelled out.

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