APIVerve

Planet Positions

PlanetPositions

Read-only

Planet Positions: Planet Positions locates solar system bodies for any observer coordinates on Earth. It checks if the sun, moon, or planets sit below the horizon, while paid plans add celestial coordinates and distance. (Cost: 2 credits)

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": {
      "lat": "<lat>",
      "lon": "<lon>",
      "planet": "<planet>"
    },
    "name": "PlanetPositions"
  }
}

Input Schema

Name	Required	Description
`alt`	No	The altitude of the observer in meters
`lat`	Yes	The latitude of the observer
`lon`	Yes	The longitude of the observer
`date`	No	The date to get planetary position data for (MM-DD-YYYY)
`time`	No	The time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided
`planet`	Yes	The planet to get position data for

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safe read-only, open-world profile, and the description adds non-obvious value: the 2-credit cost, plan-tier gating (paid plans add celestial coordinates and distance), and the horizon-check behavior. It does not describe return shape, but 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.

Conciseness4/5

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

Two tight sentences with cost deferred to the end, and the key capability is front-loaded. Minor waste from the redundant 'Planet Positions: Planet Positions' restatement, but otherwise efficient.

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?

With an output schema and full schema coverage, the description carries enough for an agent to select and call the tool. The one gap is the lack of sibling differentiation against SunPosition/MoonPosition, which would help routing among similar tools.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are already fully documented. The description only adds the framing 'any observer coordinates on Earth' and does not detail the single 'planet' value or date/time formats beyond the schema.

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 verb+resource: 'locates solar system bodies for any observer coordinates on Earth' and clarifies it checks whether bodies sit below the horizon. It does not distinguish itself from siblings like SunPosition, MoonPosition, or MoonriseMoonset, so it falls just short of a 5.

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 (given coordinates and a planet, get its position/horizon status), but there is no explicit when-to-use vs. alternatives despite multiple closely related siblings. No exclusions or preconditions are stated.

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

All APIVerve tools Inspect

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.