Skip to main content
Glama
wmmg101

kilter-mcp

by wmmg101
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kilter_get_sessions

Read-only

Retrieve recent climbing sessions, grouped by calendar day, to review past performance, see what was climbed yesterday, and compare results across days.

Instructions

Return recent climbing sessions (entries grouped by calendar day), newest first.

Use when the user asks how their last session went, what they climbed yesterday, or wants to compare sessions. Each session lists angles, sends, flashes, attempts, hardest send and every climb logged that day. limit defaults to 5.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • changedInput schema / properties / limit / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of items to return."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds useful behavioral detail beyond annotations: sessions are grouped by calendar day, sorted newest first, and include angles, sends, flashes, attempts, hardest send, and all climbs logged that day.

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?

Three short sentences deliver the core behavior, use cases, return contents, and default limit without wasted words. The information is front-loaded and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema is present, annotations cover safety, and the only parameter is optional with a documented default, the description provides everything needed to select and invoke the tool correctly.

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 coverage is 100%, so the schema already documents the lone limit parameter with its default. The description restates the default but adds little semantic value beyond the structured schema.

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 clearly states the tool returns recent climbing sessions grouped by calendar day, newest first. It provides concrete use cases that distinguish it from sibling tools focused on summaries, logs, sends, and projects, though it does not explicitly name an alternative.

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 description explicitly says when to use it: when the user asks how their last session went, what they climbed yesterday, or wants to compare sessions. It lacks an explicit 'when not to use' or direct sibling comparison, but the guidance is clear.

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