Skip to main content
Glama
Sign In

Novamris

by com.novamris
OverviewDiscussionsAdmin

Explore sky events

get_sky_overview
Read-onlyIdempotent

Returns collective planetary signs and direct/retrograde motion, current Moon phase, refined stations, sign changes and principal lunar phases over one to 31 civil days. Requires an explicit viewing timezone; today resolves from the server clock in that zone. No birth details, account or chartContext required. These are global sky facts, not personal chart contacts or life-event forecasts.

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": {
      "timezone": "<timezone>"
    },
    "name": "get_sky_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNotoday
daysNo
timezoneYesConfirmed viewing timezone, not inferred birthplace or current location.

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's added detail is appropriately focused on scope and inputs. It adds useful behavioral context by explaining that the timezone must be explicit and that "today" resolves from the server clock in that zone. It does not need to explain output shape because an output schema exists.

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 compact and front-loaded: it first defines the returned sky data, then states timezone requirements and "today" behavior, then rules out unnecessary personal context. Every sentence contributes to selecting or invoking the tool correctly.

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?

Given the tool's complexity, the read-only annotations, the low parameter description coverage, and the presence of an output schema, the description supplies the necessary scope, input constraints, and exclusion from personal chart use. Nothing essential for correct selection or invocation 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 description coverage is low, so the description usefully clarifies that the timezone is an explicit viewing timezone and that "today" resolves from the server clock in that zone. It also explains the one-to-31 civil-day window covered by the days parameter, adding interpretation beyond the schema's numeric bounds.

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 verb, "Returns," and enumerates the exact global sky data provided: planetary signs, retrograde motion, Moon phase, stations, sign changes, and lunar phases. It explicitly distinguishes this from personal chart work by saying these are "global sky facts, not personal chart contacts or life-event forecasts."

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?

It gives clear usage context: a viewing timezone is required, no birth details/account/chartContext are needed, and the tool is for collective sky facts rather than personal forecasts. It excludes personal-use cases but does not explicitly name an alternative sibling tool such as get_chart for personal chart data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Novamris toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources