Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

willyweather_surf

Retrieve surf reports from WillyWeather for any location. Provide a location ID; optionally set forecast days and API key.

Instructions

Get surf report from WillyWeather.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location_id": "<location_id>"
    },
    "name": "willyweather_surf"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
api_keyNo
location_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must bear full burden. 'Get surf report' implies a read operation, but there is no mention of authentication requirements (api_key parameter), rate limits, or error behaviors. The description is too sparse to convey behavioral traits.

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

Conciseness3/5

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

The description is a single sentence with no wasted words. However, it sacrifices informativeness for brevity. It is not overly verbose, but the lack of structure and essential details makes it less effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (3 parameters, no output schema, no annotations), the description is highly incomplete. It does not explain how to use the tool, what the response looks like, or any operational details. The agent would have insufficient context to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 3 parameters with no descriptions (0% schema coverage). The description does not add any meaning about what location_id, days, or api_key represent. It fails to compensate for the missing schema descriptions, leaving the agent without essential parameter understanding.

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 'Get surf report from WillyWeather' clearly states the verb 'Get', the resource 'surf report', and the source 'WillyWeather'. It implicitly distinguishes from sibling tools like willyweather_forecast and willyweather_tide, as it focuses specifically on surf reports.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that for general forecasts or tides, other tools (willyweather_forecast, willyweather_tide) should be used. No context on prerequisites or exclusions.

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