Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Auth status

auth_status
Read-onlyIdempotent

Checks whether the developer-portal session cookie and Garmin Connect token are present, reporting their source and expiry without exposing secrets.

Instructions

Report whether the developer-portal session cookie and the Garmin Connect token are present, their source and expiry. Never returns secrets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and closed-world behavior, so the bar is lower. The description still adds real value by disclosing what is inspected (cookie plus token), what metadata accompanies the answer (source and expiry), and the safety guarantee that secrets are never returned - a disclosure an agent could not get from the annotations.

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 short sentences with zero filler, leading with the action and ending with the safety constraint. Every clause carries information.

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?

With no output schema, the description must convey return content, and it covers the essential fields (presence, source, expiry) plus the no-secrets guarantee. It stops short of the actual response shape or what a partial-auth state looks like, which is a minor gap for a zero-parameter status check.

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 disambiguate; baseline applies. Nothing in the description misleads about inputs.

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 ("Report whether") and the exact resources checked: the developer-portal session cookie and the Garmin Connect token. It also names what is reported (presence, source, expiry), which cleanly separates it from the sibling auth_login action.

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 usage context is only implied - an agent can infer this is a pre-flight check before calling tools that require credentials, but the description never says when to call it or that auth_login is the alternative when credentials are missing. No explicit when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.