Skip to main content
Glama
wmmg101

kilter-mcp

by wmmg101
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kilter_get_sends

Read-only

Retrieve climbs the user has topped (sent), newest first. Filter by angle, date range, or limit to analyze completed ascents and flash performances.

Instructions

Return climbs the user has topped (sent), newest first.

Use when the user asks about their sends, ticks, completed climbs or flashes. Entries with status 'flash' were topped on the first try. Filters: limit (default 25, max 500), angle (degrees), start_date/end_date (YYYY-MM-DD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleNoWall angle in degrees (e.g. 20, 30, 40). Omit for all angles.
limitNoMaximum number of items to return.
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. Changed5 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."
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond the annotations: it explains the 'flash' status semantics ('topped on the first try'), the ordering ('newest first'), and the date/angle/limit filters. This is useful for an agent deciding whether the tool matches the user's intent.

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 compact and front-loaded: the core purpose is in the first sentence, the usage context in the second, and the filter summary in the third. Every sentence earns its place, and there is no redundant or filler content.

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?

The tool has an output schema, so return values need not be described. The description covers the main behavioral aspects (ordering, flash semantics, filters) and the annotations cover safety. The only minor gap is that it does not explicitly mention pagination or the meaning of 'openWorldHint', but for a read-only list tool with a rich schema, this is sufficient.

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%, so the schema already documents all four parameters. The description adds a small amount of extra meaning by restating the limit default and range and the date format, but it does not go beyond what the schema already provides. Baseline 3 is appropriate because the schema carries the heavy lifting.

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 ('Return climbs the user has topped (sent)'), a clear resource (sends), and an ordering constraint (newest first). It also distinguishes itself from siblings by explicitly mentioning 'sends, ticks, completed climbs or flashes', which maps to the tool's domain and differentiates it from kilter_get_logs, kilter_get_projects, and kilter_get_hardest_sends.

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 context for when to use the tool ('when the user asks about their sends, ticks, completed climbs or flashes') and includes a useful clarification about flash status. It does not explicitly name alternative tools or state when not to use it, but the sibling list and the domain-specific phrasing make the intended usage clear enough.

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