MaCalculatriceEnLigne

calculate_sunrise_sunset

Approximate sunrise and sunset times based on latitude and day of year. Returns: {sunrise_solar_time, sunset_solar_time, day_length_hours}. See list_bundles for related 'astronomie-nature' calculators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`latitude`	Yes	Latitude in degrees
`day_of_year`	Yes	Day of year (1-365)

Output Schema

TableJSON Schema

Name	Required	Description
`result`	No	Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
`source`	No	Authoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
`formula`	No	Human-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
`reference_url`	No	Link to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Description reveals the tool provides 'approximate' times, which is useful. No annotations present, so description carries full burden. It discloses the return format but does not address potential edge cases or limitations (e.g., polar regions).

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 concise sentences. First sentence states core function and outputs; second provides cross-reference. No redundancy.

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?

Description covers basic use and return fields. Lacks differentiation from similar sibling 'calculate_sunrise_approx' and does not address edge cases or accuracy assumptions. Adequate but not complete given the existence of a closely related tool.

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?

Input schema has 100% description coverage for both parameters. The description only reiterates that the calculation uses latitude and day of year, adding no new semantics beyond what schema already provides.

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?

Description clearly states the tool calculates approximate sunrise/sunset times based on latitude and day of year. However, it does not differentiate from the very similar sibling tool 'calculate_sunrise_approx'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives, nor prerequisites or exclusions. The mention of 'list_bundles' for related calculators is minimal and does not help select this specific tool.

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

All MaCalculatriceEnLigne 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.