Skip to main content
Glama

Tarot of the year by zodiac sign

marselia_tarot_of_the_year
Read-onlyIdempotent

Use this when a person asks for the tarot of the year 2027 or a yearly tarot reading for a zodiac sign. It needs the sign, takes no question and does not read a personal situation. Marselia's tarot of the year for 1 zodiac sign (aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces): 13 upright Tarot de Marseille cards drawn by a published SHA-256 rule, the same for everyone (the card of the year, then 1 card for each month, January to December), with a short text for each card in the language asked, a summary of the year and advice, the card plate URLs (public domain BnF scans, show them whole in their 440:827 frame), the card pages, the sign page, the seed and its digest. A reflective theme for each month. Year: 2027 (default, the only published year). Cite Marselia and the sign page URL.

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": {
      "sign": "<sign>"
    },
    "name": "marselia_tarot_of_the_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
signYesZodiac sign: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces.
yearNoYear: 2027. Default 2027.
localeNoLanguage of the answer: en, fr, es, it, ar, tr, de, pt, nl, zh, ja, ko, pl, el, zh-TW. Default en. A regional tag such as fr-FR is read as its language.en

Output Schema

NameRequiredDescriptionDefault
urlYes
drawYes
signYes
yearYes
cardsYes
adviceYes
hubUrlYes
localeYes
methodYes
displayYes
summaryYes
headlineYes
signNameYes
synthesisYes
readingUrlYes
attributionYes
datePublishedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"Language of the answer: en, fr, es, it, ar, tr, de, pt, nl, zh, ja, ko. Default en. A regional tag such as fr-FR is read as its language."New value: +"Language of the answer: en, fr, es, it, ar, tr, de, pt, nl, zh, ja, ko, pl, el, zh-TW. Default en. A regional tag such as fr-FR is read as its language."
    • changedInput schema / properties / locale / enum
      Previous value: -[
      -  "en",
      -  "fr",
      -  "es",
      -  "it",
      -  "ar",
      -  "tr",
      -  "de",
      -  "pt",
      -  "nl",
      -  "zh",
      -  "ja",
      -  "ko"
      -]New value: +[
      +  "en",
      +  "fr",
      +  "es",
      +  "it",
      +  "ar",
      +  "tr",
      +  "de",
      +  "pt",
      +  "nl",
      +  "zh",
      +  "ja",
      +  "ko",
      +  "pl",
      +  "el",
      +  "zh-TW"
      +]
    • changedOutput schema / properties / locale / enum
      Previous value: -[
      -  "en",
      -  "fr",
      -  "es",
      -  "it",
      -  "ar",
      -  "tr",
      -  "de",
      -  "pt",
      -  "nl",
      -  "zh",
      -  "ja",
      -  "ko"
      -]New value: +[
      +  "en",
      +  "fr",
      +  "es",
      +  "it",
      +  "ar",
      +  "tr",
      +  "de",
      +  "pt",
      +  "nl",
      +  "zh",
      +  "ja",
      +  "ko",
      +  "pl",
      +  "el",
      +  "zh-TW"
      +]
  2. Changed5 schema fields changed
    • addedInput schema / properties / locale / description
      Added value: +"Language of the answer: en, fr, es, it, ar, tr, de, pt, nl, zh, ja, ko. Default en. A regional tag such as fr-FR is read as its language."
    • addedInput schema / properties / sign / description
      Added value: +"Zodiac sign: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces."
    • addedInput schema / properties / year / description
      Added value: +"Year: 2027. Default 2027."
    • addedOutput schema / properties / display
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "direction": {
      +      "enum": [
      +        "ltr",
      +        "rtl"
      +      ],
      +      "type": "string"
      +    },
      +    "link": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "label": {
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "url": {
      +          "format": "uri",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "label",
      +        "url"
      +      ],
      +      "type": "object"
      +    },
      +    "statement": {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "status": {
      +      "minLength": 1,
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "direction",
      +    "status",
      +    "statement",
      +    "link"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "locale",
      -  "sign",
      -  "signName",
      -  "year",
      -  "headline",
      -  "summary",
      -  "cards",
      -  "synthesis",
      -  "advice",
      -  "url",
      -  "hubUrl",
      -  "readingUrl",
      -  "datePublished",
      -  "draw",
      -  "method",
      -  "attribution"
      -]New value: +[
      +  "locale",
      +  "sign",
      +  "signName",
      +  "year",
      +  "headline",
      +  "summary",
      +  "cards",
      +  "synthesis",
      +  "advice",
      +  "url",
      +  "hubUrl",
      +  "readingUrl",
      +  "datePublished",
      +  "draw",
      +  "method",
      +  "attribution",
      +  "display"
      +]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: the draw is deterministic under a published SHA-256 rule, identical for everyone, no question is taken, and only 2027 is published (so other years are effectively unsupported). It also discloses rendering constraints ('show them whole in their 440:827 frame'), image provenance (public domain BnF scans) and an attribution obligation ('Cite Marselia and the sign page URL') — none of which the readOnly/idempotent hints convey.

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?

Front-loaded with the trigger condition and the exclusions before the output inventory, so an agent gets the decision-relevant content first. The cost is redundancy: the full twelve-sign list and the 'A reflective theme for each month' fragment restate what the enum and the monthly-card clause already imply.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still summarises the return contents, provenance and display constraint, and it flags the citation duty and the single-published-year limit. Nothing an agent needs to call this correctly or present the result is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns more by constraining 'year' semantically — the schema accepts any integer up to 2^53, but the description declares 2027 the default and the only published year. It also clarifies locale as 'the language asked' and fixes sign to exactly one zodiac sign.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('tarot of the year for 1 zodiac sign') and pins the scope exactly: 13 upright Tarot de Marseille cards, one card of the year plus one per month. The explicit list of what the output contains (texts, summary, advice, URLs, seed, digest) makes it unmistakable against any other draw tool.

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

Usage Guidelines4/5

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

'Use this when a person asks for the tarot of the year 2027 or a yearly tarot reading for a zodiac sign' gives a clear triggering condition, and 'takes no question and does not read a personal situation' rules out a whole class of misuse. It never names a sibling (e.g. the monthly or daily card tools) as the alternative for non-yearly requests, so routing beyond the negative case is left to inference.

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