Skip to main content
Glama
Sign In
Cotlet.dev

Cotlet.dev

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

garmin_guide

Guides you through Garmin Connect screens and the sign-in link so you can work with workouts and training data; call this first before other Garmin Connect actions.

Instructions

How to work in Garmin Connect (workouts and training data): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Garmin Connect, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It implies the tool provides guidance and a sign-in link, but it does not state whether it is read-only, what exactly is returned, or whether any session/auth state is required.

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?

It is a single efficient sentence with no wasted words, and the key usage directive is clear. The ordering places content before the call-to-action, but it remains easy to parse.

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?

For a low-complexity single-parameter guide tool, the description covers the basic purpose and ordering. However, without annotations or an output schema, it should clarify the read-only nature and what the agent receives in return.

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?

There is one optional parameter with 100% schema description coverage, so the schema already documents the 'task' parameter. The description adds no parameter-specific meaning; baseline 3 applies because schema coverage is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it explains how to work in Garmin Connect and mentions screens and a sign-in link, so an agent can infer it is an orientation/guide tool. But it does not use a specific verb+resource like 'returns setup instructions' and remains somewhat vague about whether it returns documentation, a link, or both.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The directive 'Call this first' gives clear sequencing guidance that distinguishes it from the sibling action tools. It does not name exclusions or alternatives, but the primary condition for use is explicit.

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