MaCalculatriceEnLigne

calculate_sunrise_approx

Estimate sunrise/sunset times for a latitude on a given day of year. Use for astronomy or outdoor planning. Inputs: latitude, day of year. Returns sunrise/sunset hours, daylight duration. See list_bundles for related 'astronomie-nature' calculators.

Input Schema

TableJSON Schema

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

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

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It states 'Estimate' implying approximation, and lists return values (sunrise/sunset hours, daylight duration). It does not disclose any limitations, accuracy, or edge cases, which is acceptable for a simple calculator but not exhaustive.

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?

The description is concise with two sentences covering purpose, usage, inputs, and outputs. It is front-loaded and avoids unnecessary detail. The reference to list_bundles adds helpful context without bloating.

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?

Given the simple two-parameter input and existence of an output schema (implied), the description adequately covers the tool's functionality and return values. It also directs to related calculators. It is complete for a straightforward estimation 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?

The input schema already describes both parameters with 100% coverage. The description repeats 'Inputs: latitude, day of year' adding no new meaning. It does not provide additional constraints or format details 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?

The description clearly states the tool estimates sunrise/sunset times for a latitude and day of year. The verb 'Estimate' and resource 'sunrise/sunset times' are specific. However, it does not explicitly differentiate from the sibling 'calculate_sunrise_sunset' which may offer more precision, relying only on the 'approx' in the name.

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 description mentions using for astronomy or outdoor planning, providing context. However, it offers no guidance on when not to use this tool or alternatives. The sibling 'calculate_sunrise_sunset' is not referenced or contrasted.

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.