Skip to main content
Glama
Sign In
skylight-mcp

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_search_chores

Read-only

Search chores by text query, including unscheduled and template chores that date-range lists cannot return.

Instructions

Search chores (incl. unscheduled/template chores the date-range list can't return).

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": {
      "search_query": "<search_query>"
    },
    "name": "skylight_search_chores"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
frameIdNo
search_queryYesText to search chore summaries.
include_up_for_grabsNo
ended_chore_lookback_daysNoHow many days back to include ended chores.

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. First observedv0.4.6

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that the search reaches unscheduled/template chores, but says nothing about pagination (the limit param), result ordering, or how broad open-world search behaves.

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?

A single front-loaded sentence with a parenthetical that earns its place by carrying the key scoping distinction. No filler, nothing redundant.

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

Completeness3/5

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

For a 5-parameter, no-output-schema search tool this is only half-sufficient: the high-level scope is clear, but three undocumented parameters and no return-format guidance leave real gaps. It is minimally viable but not complete.

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 coverage is only 40%: limit, frameId, and include_up_for_grabs have no description in the schema or the tool description. The mention of unscheduled/template chores loosely gestures at include_up_for_grabs but never explains limit, frameId scoping, or the meaning of the required search_query beyond the schema's own text.

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

Purpose4/5

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

"Search chores" gives a specific verb and resource, and the parenthetical explicitly scopes it to unscheduled/template chores that the date-range list cannot return, which distinguishes it from skylight_list_chores. It stops short of naming that sibling tool directly, so the differentiation requires a small inference.

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

Usage Guidelines3/5

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

It implies when to reach for this tool — when you need template/unscheduled chores excluded from the date-range list — but never states an explicit alternative or the conditions that select between them. The routing hint is real but implicit rather than a clear use-this-not-that rule.

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