Skip to main content
Glama
wmmg101

kilter-mcp

by wmmg101
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kilter_get_progression

Read-only

Track climbing progression over time with monthly or weekly stats on sessions, sends, flashes, and attempts. Filter by wall angle to see trends and identify improvement.

Instructions

Return climbing progression over time, oldest period first.

Use when the user asks how they have progressed, trends, whether they are improving, or for a month-by-month/week-by-week view. period is 'month' (default) or 'week'. Each period has sessions, sends, unique climbs, flashes, attempts and hardest send/flash. Optional wall-angle filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleNoWall angle in degrees (e.g. 20, 30, 40). Omit for all angles.
periodNoBucket size for the progression: calendar month or ISO week.month

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / period / description
      Added value: +"Bucket size for the progression: calendar month or ISO week."
    • addedInput schema / properties / period / enum
      Added value: +[
+  "month",
+  "week"
+]
  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?

Beyond the readOnlyHint and destructiveHint annotations, the description adds meaningful behavior: results are ordered 'oldest period first,' each period contains specific aggregates, and angle filtering is optional. This gives the agent a useful preview of response semantics without contradicting 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?

The description is tightly written and well-structured: purpose first, then when-to-use, then parameter clarification, then output contents. Every sentence earns its place with no redundancy.

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?

The tool has only two optional parameters, a full input schema, and an output schema. The description covers purpose, usage triggers, period semantics, output fields, and the optional angle filter. Nothing essential is missing for an agent to select and invoke it 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 both parameters. The description adds marginal value by restating period's default ('month') and calling angle an optional filter, but it does not introduce new semantic detail beyond the 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 states a specific verb and resource: 'Return climbing progression over time, oldest period first.' This clearly identifies the tool's function. It does not explicitly name and distinguish sibling tools, but the time-based progression focus sets it apart from the summary, logs, sends, and pyramid siblings.

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 provides clear usage context: 'Use when the user asks how they have progressed, trends, whether they are improving, or for a month-by-month/week-by-week view.' This is explicit about when to use the tool, though it does not mention when not to use it or name alternatives.

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