Skip to main content
Glama
Sign In
skylight-mcp

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_redeem_reward

Redeem a reward on Skylight Calendar using the reward ID, with optional member and frame details.

Instructions

Redeem a reward.

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": {
      "id": "<id>"
    },
    "name": "skylight_redeem_reward"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
frameIdNo
category_idNoMember redeeming, if required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv0.7.1
    • removedInput schema / properties / category_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / category_id / type
      Added value: +[
+  "string",
+  "number"
+]
  3. First observedv0.4.6

TDQS

D1.7/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, which tells the agent this is a non-destructive write. The description adds nothing beyond that: it doesn't say whether points are deducted, whether redemption is idempotent, whether it can fail for insufficient balance, or what state changes result.

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

Conciseness2/5

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

A three-word sentence is short but not usefully concise — this is under-specification, not efficient communication. There is no front-loaded scope, prerequisite, or result information to earn the brevity.

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?

A mutation tool with no output schema, 33% parameter coverage, no usage guidance, and no side-effect disclosure is not complete enough for an agent to invoke it correctly. Nothing describes what a successful redemption does to the reward or the member's points.

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

Parameters2/5

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

Schema description coverage is only 33%: id and frameId are undocumented, and the lone documented field (category_id) carries a confusing description ("Member redeeming, if required.") that doesn't match its name. The description adds no parameter meaning whatsoever to compensate for the gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Redeem a reward." is a verbatim restatement of the tool name skylight_redeem_reward, adding no distinguishing information. It doesn't differentiate from the many sibling reward tools (skylight_unredeem_reward, skylight_get_reward, skylight_add_reward_points), so an agent gains nothing beyond what the name already says.

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

Usage Guidelines1/5

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

No guidance on when to use this versus skylight_unredeem_reward, skylight_get_reward, or skylight_add_reward_points. No preconditions, no state requirements (e.g., sufficient points balance), no indication of what triggers a valid redemption.

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