Skip to main content
Glama
Sign In
cobus-meyer

table-mountain-mcp

by cobus-meyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Best day to go up Table Mountain

find_best_day
Read-onlyIdempotent

Rank days in Table Mountain's 7-day forecast by weather quality and good climbing hours, so you can choose a suitable day or check specific dates and ranges.

Instructions

Rank the days in tablemountainweather.com's 7-day Table Mountain forecast, best first. Each day has a quality rating (best to worst: excellent, good, grey, poor, blocked) and goodHours, the number of hours that day rated good for going up. Use for 'which day is best', 'is Saturday any good', or planning a trip this week. Pass dates for specific days, or from/to for a range; with no arguments it ranks every remaining day. Convert weekday names to YYYY-MM-DD using freshness.todayInCapeTown from any earlier result, or call with no arguments and read the weekday field. Dates outside the forecast come back in notInForecast: say there's no forecast for them yet instead of guessing. If cablewayNote is set, mention it.

Input Schema

NameRequiredDescriptionDefault
toNoLast date to include, YYYY-MM-DD (Cape Town).
fromNoFirst date to include, YYYY-MM-DD (Cape Town). Defaults to today.
datesNoSpecific dates to rate, YYYY-MM-DD (Cape Town). Overrides from/to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, openWorld); the description adds substantial behavior beyond them: the rating scale, `goodHours`, the `notInForecast` fallback for out-of-range dates, the `cablewayNote` caveat, and the dependency on `freshness.todayInCapeTown` for weekday-to-date conversion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and rating scale, then argument guidance, then edge-case handling; nearly every sentence carries instructions the agent needs at call time. It runs a bit long, but no sentence is filler.

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?

There is no output schema, and the description compensates by naming every meaningful return field (quality, goodHours, notInForecast, cablewayNote, weekday) and telling the agent how to phrase results. Nothing needed to call or interpret it is missing.

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 baseline is 3, and the description adds real meaning on top: precedence between `dates` and `from`/`to` and the no-argument default of ranking every remaining day. The weekday-name conversion workflow is value the schema cannot express.

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?

States a specific verb and resource ('Rank the days ... 7-day Table Mountain forecast, best first') and enumerates the rating vocabulary up front. The 7-day ranking scope implicitly separates it from the today-only sibling, so an agent can pick correctly without opening the schema.

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?

Gives concrete triggering phrasings ('which day is best', 'is Saturday any good') plus explicit argument-selection rules: use `dates` for specific days, `from`/`to` for a range, nothing to rank all remaining days. It never names the sibling `get_table_mountain_today` as the alternative for today's conditions, so the when-not guidance is incomplete.

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