Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

session_start

Report whether the server adopted a simulator left by an earlier session or started clean. Set reset to true to terminate the adopted simulator and clear stored session state.

Instructions

Report whether this server adopted a simulator left by an earlier session or started clean. Use reset: true to terminate the adopted simulator and clear the stored session.

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

Input Schema

NameRequiredDescriptionDefault
resetNoTerminate the adopted simulator and clear session state (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the important behavioral fact: by default the call is a report, while reset: true destroys the adopted simulator and clears stored session state. That destruction disclosure is exactly the context an agent needs. What is missing is the failure/no-op case — whether reset: true on a clean server is harmless — and any hint of the shape of the report.

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 sentences, zero filler, and the core purpose is front-loaded ahead of the optional destructive flag. Every clause carries information an agent needs.

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 single-optional-boolean tool with full schema coverage and no output schema, the description covers purpose and the destructive path adequately. The remaining gap is modest: it never says what a 'clean' versus 'adopted' report looks like or whether reset is safe when nothing was adopted.

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 description coverage is 100% and the single parameter's schema text already says 'Terminate the adopted simulator and clear session state (default: false)'. The description's reset clause largely restates that, adding no syntax, preconditions, or side-effect detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and outcome — 'Report whether this server adopted a simulator left by an earlier session or started clean' — which is concrete enough that an agent knows exactly what it gets back conceptually. It does not, however, distinguish this from siblings such as reset_state or launch_simulator, so an agent comparing the two must infer the boundary itself.

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?

Usage is only implied: the framing of 'an earlier session' suggests calling it at session start, but the description never says so explicitly and names no alternatives. The one explicit routing instruction ('Use reset: true to...') governs a parameter, not the choice of this tool over another.

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