Панчанга в любом месте: city/geonameid, не оба; sun_state/sun_unavailable.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | ||
| date | No | ||
| lang | No | ru | |
| detailed | No | ||
| podrobno | No | ||
| geonameid | No |
| Name | Required | Description | Default |
|---|---|---|---|
| sun_state | Yes | ||
| sun_unavailable | No |
Changes observed during successful MCP inspections.
Output schema / descriptionRemoved value: -"Машинная схема ответа панчанги; все поля необязательны из-за старых клиентов/API."Output schema / properties / chem_poschitanoRemoved value: -{}Output schema / properties / choghadiya_dayRemoved value: -{}Output schema / properties / choghadiya_nightRemoved value: -{}Output schema / properties / cityRemoved value: -{}Output schema / properties / computed_at_utcRemoved value: -{}Output schema / properties / computed_withRemoved value: -{}Output schema / properties / dateRemoved value: -{}Output schema / properties / gulika_kaalRemoved value: -{}Output schema / properties / karanaRemoved value: -{}Output schema / properties / linkRemoved value: -{}Output schema / properties / link_reasonRemoved value: -{}Output schema / properties / nakshatraRemoved value: -{}Output schema / properties / next_sunriseRemoved value: -{}Output schema / properties / not_availableRemoved value: -{}Output schema / properties / place_usedRemoved value: -{}Output schema / properties / rahu_kaalRemoved value: -{}Output schema / properties / sun_noteRemoved value: -{}Output schema / properties / sun_state / descriptionRemoved value: -"Состояние солнечных суток; полярный режим — не bad_date."Output schema / properties / sun_state / typePrevious value: -[
- "string",
- "null"
-]New value: +"string"Output schema / properties / sun_unavailable / descriptionRemoved value: -"Солнечно-зависимые поля, недоступные при ненормальных солнечных сутках."Output schema / properties / sunriseRemoved value: -{}Output schema / properties / sunsetRemoved value: -{}Output schema / properties / tithiRemoved value: -{}Output schema / properties / varaRemoved value: -{}Output schema / properties / yamagandaRemoved value: -{}Output schema / properties / yogaRemoved value: -{}Output schema / requiredAdded value: +[
+ "sun_state"
+]Output schema / descriptionAdded value: +"Машинная схема ответа панчанги; все поля необязательны из-за старых клиентов/API."Output schema / propertiesAdded value: +{
+ "chem_poschitano": {},
+ "choghadiya_day": {},
+ "choghadiya_night": {},
+ "city": {},
+ "computed_at_utc": {},
+ "computed_with": {},
+ "date": {},
+ "gulika_kaal": {},
+ "karana": {},
+ "link": {},
+ "link_reason": {},
+ "nakshatra": {},
+ "next_sunrise": {},
+ "not_available": {},
+ "place_used": {},
+ "rahu_kaal": {},
+ "sun_note": {},
+ "sun_state": {
+ "description": "Состояние солнечных суток; полярный режим — не bad_date.",
+ "enum": [
+ "normal",
+ "polar_day",
+ "polar_night",
+ "transition",
+ "unknown"
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "sun_unavailable": {
+ "description": "Солнечно-зависимые поля, недоступные при ненормальных солнечных сутках.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "sunrise": {},
+ "sunset": {},
+ "tithi": {},
+ "vara": {},
+ "yamaganda": {},
+ "yoga": {}
+}Input schema / properties / city / defaultRemoved value: -nullInput schema / properties / date / defaultRemoved value: -nullInput schema / properties / geonameid / defaultRemoved value: -nullOutput schema / additionalPropertiesRemoved value: -trueOutput schema / titleRemoved value: -"panchangaDictOutput"Input schema / properties / city / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Input schema / properties / date / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Input schema / properties / geonameid / typePrevious value: -"integer"New value: +[
+ "integer",
+ "null"
+]Input schema / properties / city / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / city / titleRemoved value: -"City"Input schema / properties / city / typeAdded value: +"string"Input schema / properties / date / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / date / titleRemoved value: -"Date"Input schema / properties / date / typeAdded value: +"string"Input schema / properties / detailed / titleRemoved value: -"Detailed"Input schema / properties / geonameid / anyOfRemoved value: -[
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
-]Input schema / properties / geonameid / titleRemoved value: -"Geonameid"Input schema / properties / geonameid / typeAdded value: +"integer"Input schema / properties / lang / titleRemoved value: -"Lang"Input schema / properties / podrobno / titleRemoved value: -"Podrobno"Input schema / titleRemoved value: -"panchangaArguments"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden, yet it discloses nothing about read-only vs. mutation behavior, permissions, rate limits, or what 'sun_state/sun_unavailable' means. The agent cannot infer behavioral traits from this text.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact sentence with no filler, and the tool name is front-loaded. Every word is used, though the structure is cryptic rather than helpful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 6 parameters, no annotations, and 0% schema description coverage, the description is far too sparse to be complete. It does not explain the tool's purpose, when to use it, or what most parameters mean, despite an output schema existing for return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for 6 parameters, and the description only notes the mutual exclusivity of city and geonameid. It says nothing about date, lang, detailed, podrobno, or even confirms what city/geonameid represent, failing to compensate for the absence of schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Панчанга в любом месте' merely restates the tool name with a location modifier. It states no verb or resource beyond the name, leaving the tool's actual function (calculation? lookup? list?) unexplained and indistinguishable from siblings like muhurta_search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives a partial constraint ('city/geonameid, не оба') but no guidance on when to use this tool versus alternatives such as muhurta_search or natal_chart. The cryptic 'sun_state/sun_unavailable' fragment offers no actionable usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.