Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_device_last_used

Read-only

Returns the Garmin device used most recently, helping resolve a missing device ID when pushing a workout to a device.

Instructions

The device used most recently. Also used internally by pushWorkoutToDevice to resolve a missing deviceId.

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_device_last_used"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/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 no behavioral context of its own — no indication of what the returned device object contains, whether it requires an authenticated user, or what happens when no device has ever been used.

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?

Two very short sentences with the primary purpose front-loaded. The second sentence about internal use is borderline — it serves the agent somewhat by signaling this is an implementation helper, but it reads as leakage from another tool's code rather than agent-facing information.

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 zero parameters and no output schema, the description is the only place an agent could learn the shape of the return value (a device record with id/name/etc.), and it does not provide that. Annotations cover safety, but the missing return-value context leaves a real gap for a lookup tool.

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 there is nothing for the description to clarify. The 4 baseline applies: no ambiguity is introduced and no parameter semantics are needed.

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 names the exact resource returned ('the device used most recently'), which distinguishes it implicitly from the sibling get_primary_training_device (a different concept). It lacks an explicit verb (e.g., 'Returns/Retrieves'), making it a fragment rather than a full purpose statement, but an agent can still infer the tool's contract.

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?

There is no explicit guidance on when an agent should call this versus get_devices or get_primary_training_device. The note that it is 'used internally by pushWorkoutToDevice' describes another tool's implementation, not a decision rule the agent can apply.

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