Skip to main content
Glama
wmmg101

kilter-mcp

by wmmg101
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kilter_get_hardest_sends

Read-only

Retrieve your hardest sent climbs sorted by grade, with optional wall-angle filtering and adjustable result limit.

Instructions

Return the user's hardest sent climbs (unique per climb and angle), hardest first.

Use when the user asks about their hardest sends, best climbs, max grade, or personal bests. Optional wall-angle filter; limit defaults to 10.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleNoWall angle in degrees (e.g. 20, 30, 40). Omit for all angles.
limitNoMaximum number of items to return.

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."
    • 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.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful behavioral detail beyond those: results are unique per climb and angle, sorted hardest first, with an optional wall-angle filter. This gives the agent meaningful expectations about the tool's behavior without contradicting the 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 two concise, front-loaded sentences: the first states exactly what the tool returns, and the second gives usage triggers and parameter guidance. There is minimal redundancy, and the key differentiating behavior is presented first.

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 simple read-only tool with two optional parameters and an existing output schema, the description is complete. It covers purpose, usage triggers, deduplication behavior, ordering, and the optional angle filter, and the annotations cover safety, making it sufficient for correct invocation.

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 baseline is 3; the schema already documents angle and limit, including defaults. The description mentions the optional wall-angle filter and the default limit, but this largely duplicates the schema rather than adding new semantic meaning.

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 action ('Return') and a precise resource: the user's hardest sent climbs, with uniqueness per climb and angle, ordered hardest first. This clearly separates it from siblings like kilter_get_sends or kilter_get_grade_pyramid by focusing on 'hardest sends, best climbs, max grade, or personal bests.'

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 'Use when the user asks about their hardest sends, best climbs, max grade, or personal bests,' providing clear context for when this tool should be selected. It does not mention when not to use it or name an alternative, but the use-case guidance is specific enough to route an agent 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