Skip to main content
Glama

AstroWay Divination and esoterica

Haab Civil Day

astroway_mayan_haab
Read-onlyIdempotent

365-day civil calendar = 18 months × 20 days + 5-day Wayeb. Identifies if date falls in unlucky Wayeb period.

[Group: Mayan Calendars] [Endpoint: POST /v1/mayan/haab] [Required: date] [Cost: 10 credits (Tier 1)]

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": {
      "date": "<date>"
    },
    "name": "astroway_mayan_haab"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
haabNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / haab / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "day": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "isWayeb": {
      -        "anyOf": [
      -          {
      -            "type": "boolean"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "label": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "month": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "day": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "isWayeb": {
      +        "type": [
      +          "boolean",
      +          "null"
      +        ]
      +      },
      +      "label": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "month": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered and the description does not contradict it. The description adds a per-call cost ('10 credits (Tier 1)') and the endpoint, which are genuinely useful behavioral facts for an agent budgeting calls. Beyond that it is a calendar primer rather than disclosure of behavior, and it says nothing about what the response contains or how the Wayeb flag is expressed, though an output schema exists to cover the latter.

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 front-loaded sentences state the calendar structure and the one interpretive result, followed by a compact bracketed metadata block (group, endpoint, required, cost). Nothing is padded, though the bracketed lines duplicate structured fields (required parameter, endpoint naming) that the schema and name already convey.

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?

An output schema exists, so return values need not be described, and the annotations carry the safety profile. What is missing for a 3-parameter date-conversion tool is the input-date interpretation (calendar system, boundary behavior), any explicit routing against the seven other Mayan siblings, and confirmation of what the Wayeb determination returns. It is adequate to guess how to call it but not self-sufficient for correct selection.

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

Parameters2/5

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

Schema description coverage is 67%; `fields` and `precision` are documented in the schema, but the one required parameter, `date`, carries only a regex pattern and no prose. The description's '[Required: date]' merely repeats the schema's required list and never clarifies whether the date is a Gregorian input converted to Haab, how time zone or midnight boundaries are handled, or what the output does when the date is in Wayeb — the single most important semantic question for this tool. It adds no meaning beyond the schema for any parameter.

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 defines the specific resource — the 365-day Haab civil calendar of 18×20 days plus Wayeb — and states the concrete output of interest ('identifies if date falls in unlucky Wayeb period'), so an agent knows this computes Haab position for a date. It does not name sibling alternatives such as astroway_mayan_tzolkin, astroway_mayan_long_count, or astroway_mayan_full, so the Tzolkin-vs-Haab distinction must be inferred from the calendar arithmetic rather than stated.

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 only implied: the Wayeb sentence hints at one use case (checking for the unlucky five days), and the group/endpoint tags place it in the Mayan family. There is no explicit when-to-use versus astroway_mayan_full or the other Mayan siblings, and no guidance on prerequisites or when a caller would want the full calendar instead of just Haab.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources