Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Fixed star catalogue

astroway_aspects_fixed_stars_catalog
Read-onlyIdempotent

Lists the 953 fixed stars the API accepts, including traditional names, Bayer codes, constellations, magnitudes and the 36-star astrological default set. Filter by maximum magnitude to return only brighter stars.

Instructions

The star names this API accepts, from our fixed-star catalogue (953 stars): traditional name, Bayer nomenclature, constellation and magnitude, with the 36-star astrological default set flagged. Optional ?maxMagnitude= trims to the bright end. Static lookup, no chart needed.

[Group: Aspects & Points] [Endpoint: GET /v1/fixed-stars/catalog] [Cost: 5 credits (Tier ½)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_aspects_fixed_stars_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countNo
starsNo
totalNo
sourceNo
maxMagnitudeNo
defaultSetSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds genuinely new behavioral facts: catalogue size (953), the composition of each entry, the flagged 36-star astrological default set, the bright-end trimming behavior, and the credit cost.

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 statement and the differentiator early; every sentence contributes information. The trailing bracketed [Group]/[Endpoint]/[Cost] boilerplate is metadata rather than description, but it is brief and does not obscure the main content.

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

Completeness4/5

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

An output schema exists, so return values need not be re-explained, yet the description still usefully summarizes entry fields. For a zero-parameter static lookup this is close to complete; only the maxMagnitude format/default and not-found behavior are 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?

The input schema has zero properties, so the baseline is 4, and the description goes further by documenting an optional `?maxMagnitude=` query parameter that does not appear in the schema at all. It explains direction ('trims to the bright end') but gives no default value or numeric range, which keeps it short of 5.

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?

States a specific resource and verb: the star names this API accepts, sourced from a 953-star catalogue, with the returned fields enumerated. The phrase 'Static lookup, no chart needed' implicitly separates it from chart-based siblings such as astroway_aspects_fixed_stars, though no sibling is named outright.

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?

Usage is implied rather than spelled out: an agent learns this is the place to resolve/validate star names and that no chart is required. There is no explicit when-not condition, no named alternative, and no statement about what to do if a name is not found in the catalogue.

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