Skip to main content
Glama
wmmg101

kilter-mcp

by wmmg101
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kilter_get_logs

Read-only

Retrieve your Kilter Board climbing history with entries sorted newest first. Filter by date, wall angle, or send status to review sessions, sends, or attempts.

Instructions

Return the user's Kilter logbook entries, newest first.

Use when the user asks about recent Kilter climbs, attempts, what they climbed on a date, or wants raw history. Each entry is one climb at one wall angle on one date with the number of tries in that entry. Filters: limit (default 25, max 500), angle (degrees), topped (true=only sends, false=only unsuccessful attempts), start_date/end_date (YYYY-MM-DD, inclusive).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleNoWall angle in degrees (e.g. 20, 30, 40). Omit for all angles.
limitNoMaximum number of items to return.
toppedNotrue = only topped (sent) entries, false = only unsuccessful attempts.
end_dateNoInclusive end date, YYYY-MM-DD, in the user's timezone.
start_dateNoInclusive start date, YYYY-MM-DD, in the user's timezone.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +25
  2. Changed6 schema fields changedv0.2.1
    • addedInput schema / properties / angle / description
      Added value: +"Wall angle in degrees (e.g. 20, 30, 40). Omit for all angles."
    • addedInput schema / properties / end_date / description
      Added value: +"Inclusive end date, YYYY-MM-DD, in the user's timezone."
    • 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."
    • addedInput schema / properties / start_date / description
      Added value: +"Inclusive start date, YYYY-MM-DD, in the user's timezone."
    • addedInput schema / properties / topped / description
      Added value: +"true = only topped (sent) entries, false = only unsuccessful attempts."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate a safe read-only operation, and the description adds meaningful behavioral context: ordering ('newest first'), entry granularity, inclusive date filtering, and the meaning of the 'topped' filter. This goes beyond the structured annotations without contradicting them.

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 tight sentences: purpose, usage context, and filter summary. Every sentence earns its place, and the most important information is front-loaded.

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?

For a read-only tool with an output schema and five optional, well-described parameters, this description is complete. It explains when to use it, what it returns at a unit level, and how every filter behaves, so an agent can invoke it correctly without additional inference.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra value by stating the limit maximum of 500 (not present in the schema), clarifying angle units in degrees, and compactly summarizing all filter semantics including inclusive date ranges.

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?

The description states a specific verb and resource: 'Return the user's Kilter logbook entries, newest first.' It also clarifies the unit of data ('one climb at one wall angle on one date with the number of tries'), which distinguishes it from send lists, projects, summaries, and statistics tools.

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 gives clear trigger conditions: 'Use when the user asks about recent Kilter climbs, attempts, what they climbed on a date, or wants raw history.' It does not explicitly name alternative tools or state when not to use it, but the context is specific enough for an agent to route correctly.

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