Skip to main content
Glama

Tarot of the month by zodiac sign

marselia_tarot_of_the_month
Read-onlyIdempotent

Use this when a person asks for the tarot of the month or a monthly 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 month for 1 zodiac sign (aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces): 4 upright Tarot de Marseille cards drawn by a published SHA-256 rule, the same for everyone (the climate of the month, love, work and money, the advice of the month), with the month's text for each position in the language asked, the card plate URLs (public domain BnF scans, show them whole in their 440:827 frame), the card pages and the sign page. A reflective theme for the month. Month: YYYY-MM, default the current month in Paris; only the current and published months. 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_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
signYesZodiac sign: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces.
monthNoMonth as YYYY-MM, for example 2026-11. Default: the current month in Paris. Only the current month and the published earlier months are served.
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
cardsYes
monthYes
hubUrlYes
localeYes
methodYes
sourceYes
displayYes
summaryYes
headlineYes
signNameYes
monthLabelYes
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 / month / description
      Added value: +"Month as YYYY-MM, for example 2026-11. Default: the current month in Paris. Only the current month and the published earlier months are served."
    • addedInput schema / properties / sign / description
      Added value: +"Zodiac sign: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces."
    • 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",
      -  "month",
      -  "monthLabel",
      -  "source",
      -  "headline",
      -  "summary",
      -  "cards",
      -  "url",
      -  "hubUrl",
      -  "readingUrl",
      -  "datePublished",
      -  "draw",
      -  "method",
      -  "attribution"
      -]New value: +[
      +  "locale",
      +  "sign",
      +  "signName",
      +  "month",
      +  "monthLabel",
      +  "source",
      +  "headline",
      +  "summary",
      +  "cards",
      +  "url",
      +  "hubUrl",
      +  "readingUrl",
      +  "datePublished",
      +  "draw",
      +  "method",
      +  "attribution",
      +  "display"
      +]
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description still adds substantial behavior beyond them: the draw is a deterministic published SHA-256 rule identical for everyone, cards are always upright Tarot de Marseille, and the response includes plate URLs, card pages and the sign page. It also discloses the month availability window (current and published months only, Paris default) and an attribution requirement, which are exactly the operational constraints an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger sentence is correctly front-loaded, but the remainder is a dense run-on that packs card positions, image framing, attribution and month rules into one paragraph without separators. Presentation details such as the 440:827 frame are useful but buried, and some return-content detail duplicates the output schema.

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?

For a three-parameter tool with an output schema, the description covers everything an agent needs: when to call it, what it will not do, the deterministic nature of the draw, month availability, language handling, and a required citation. Nothing essential to a correct invocation is missing.

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?

Schema description coverage is 100% with two enums, so the schema already documents sign, month and locale fully; the description largely restates them (sign list, YYYY-MM, language of the answer). The only marginal addition is the phrase "in the language asked" and the restatement of the published-months limit. Baseline 3 applies when the schema carries the parameter burden.

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: a tarot of the month reading for exactly one zodiac sign, enumerating the twelve accepted signs and the four card positions (climate, love, work/money, advice). The scope is narrow enough that an agent can distinguish it from marselia_tarot_of_the_year or marselia_daily_card without opening another schema.

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?

Opens with an explicit trigger ("Use this when a person asks for the tarot of the month or a monthly tarot reading for a zodiac sign") and adds clear exclusions: it takes no question and does not read a personal situation. It stops short of naming a sibling for adjacent requests such as a yearly or daily reading, so the routing is clear but not fully closed.

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