Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Sun Position

SunPosition
Read-only

Sun Position: Sun Position calculates the sun altitude and azimuth, plus compass bearing, for any geographic coordinates and time. Provide latitude and longitude to read sun elevation angles and daylight status; paid plans add panel aiming angles and shadow ratios. (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>"
    },
    "name": "SunPosition"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesThe latitude of the location
lonYesThe longitude of the location
dateNoThe date to get the sun position data for (MM-DD-YYYY)
timeNoThe time of day for the calculation (HH:mm format, 24-hour), read in the timezone of the coordinates. Defaults to 00:00 if not provided
timezoneNoIANA timezone to read the date and time in, such as America/Los_Angeles. Defaults to the timezone of the coordinates

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-schema context — a 2-credit cost and paid-plan gating of extra outputs — but leaves open whether those premium fields appear in the response or how the timezone default resolves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Three sentences with no filler, and the core capability leads. However, the redundant prefix 'Sun Position: Sun Position calculates' wastes the most valuable opening real estate by repeating the title twice.

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 present, the description needn't explain return values, and annotations plus full schema coverage handle inputs and safety. Cost and tier limits are disclosed, so the only real gap is routing versus similar astronomy siblings.

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%, with formats (MM-DD-YYYY, HH:mm 24-hour), examples, and defaults for time and timezone all documented in the schema. The description only restates that latitude and longitude are supplied and adds no meaning about how date/time/timezone interact, so baseline 3 applies.

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?

The description names a concrete verb+resource pair (calculates sun altitude, azimuth, compass bearing) and scopes it to geographic coordinates and time, which is far more specific than the bare name 'SunPosition'. It does not, however, distinguish itself from near siblings such as SunriseSunset, DaylightDurationCalculator, or MoonPosition.

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?

'Provide latitude and longitude to read sun elevation angles and daylight status' implies the required inputs but gives no explicit when-to-use/when-not guidance or pointer to SunriseSunset when an agent wants only rise/set times. The paid-plan note about panel aiming angles and shadow ratios is the closest thing to a usage condition.

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

All APIVerve 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