Skip to main content
Glama
Sign In
astroway-mcp

astroway-mcp

Official
by astroway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Local Space Influence Zone

astroway_geo_local_space_influence_zone
Read-onlyIdempotent

Calculate local-space influence-zone lines for a relocated chart, showing planet directions from a specific city or location on a map.

Instructions

Calculate the local space influence zone lines for a chart relocated to a specific city: lines on the map showing planet directions from that location.

[Group: Astro-Geography] [Endpoint: POST /v1/local-space/influence-zone] [Required: latitude, longitude, azimuth] [Cost: 50 credits (Tier 3)]

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "azimuth": "<azimuth>"
    },
    "name": "astroway_geo_local_space_influence_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
azimuthYes
latitudeYes
halfAngleNo
longitudeYes
maxDistDegNo

Output Schema

NameRequiredDescriptionDefault
countNo
polygonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful operational context in the cost line ('50 credits (Tier 3)') and the required-parameter line, but says nothing about the geographic/cartographic constraints of the computation (coordinate ranges, units) beyond that.

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 definition sentence followed by a compact metadata block (group, endpoint, required, cost). Every line carries information; nothing is padded or buried.

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?

An output schema exists, so return-value explanation is not required, and cost/endpoint/required fields are supplied. However, two optional parameters remain undocumented in both schema and description, and there is no indication of coordinate conventions or units, leaving an agent unable to call the tool confidently.

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 0%, so the description carries the full burden. It only restates the three required field names from the schema and adds no meaning: azimuth is never explained (azimuth of what, in what convention), and halfAngle and maxDistDeg are not mentioned at all despite directly affecting the output lines. This is a substantial gap for a 5-parameter computation tool.

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?

A specific verb ('Calculate') plus a specific resource ('local space influence zone lines') and a clarifying gloss ('lines on the map showing planet directions from that location'). It implicitly separates itself from the sibling astroway_geo_local_space by describing a line-based map product, but never names that sibling to make the distinction explicit.

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?

The phrase 'for a chart relocated to a specific city' hints at the use case, and the Required line tells the agent what must be supplied, but there is no explicit when-to-use / when-not-to-use guidance and no routing against the many other astro-geography tools (geo_acg, geo_relocation, geo_zenith, geo_local_space).

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