Skip to main content
Glama
Sign In
Cotlet.dev

Cotlet.dev

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

garmin_status

Verify your Cotlet.dev account, available credits, and Garmin Connect connection before reading metrics or creating workouts.

Instructions

Check that your Cotlet.dev account and Garmin Connect are ready: account, credits and Garmin Connect connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the three dimensions inspected (account, credits, connection), which is the substantive behavioral content. It does not state that the call is non-mutating, whether authentication is required, or what a failing result looks like.

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 the verb first and the checked items listed after the colon; no filler. Slightly denser than needed because the branded product name adds little for tool selection.

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?

For a zero-parameter, side-effect-free status probe with no output schema, the description adequately enumerates what will be reported. The only omission is any hint of response shape or failure semantics, which is minor at this complexity.

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 and the baseline is 4. No parameter-related gaps exist.

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 a specific verb ("Check") and enumerates the concrete resources verified: Cotlet.dev account, credits, and the Garmin Connect connection. This clearly separates it from the action-oriented siblings (garmin_open, garmin_click, garmin_type, garmin_read), which manipulate a Garmin session rather than report readiness, though the description never explicitly says so.

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 when-to-use statement, no prerequisite, and no mention of alternatives among the six sibling tools. The word "ready" hints at a pre-flight check, but the agent must infer that this should be called before starting a Garmin workflow.

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