Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

RWS: Love Triangle

astroway_tarot_rider_waite_draw_love_triangle
Read-onlyIdempotent

Draw a six-card Rider-Waite tarot spread to explore three-person love dynamics, clarifying each person’s perspective, tensions, and relationship choices.

Instructions

6-card three-person love dynamics.

[Group: Tarot: Rider-Waite-Smith] [Endpoint: POST /v1/tarot/rider-waite/draw/love-triangle] [Cost: 10 credits (Tier 1)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_tarot_rider_waite_draw_love_triangle"
  }
}

Input Schema

NameRequiredDescriptionDefault
artNoCard art set, e.g. rws-1909, rws-restored, rws-vector. GET /v1/tarot/decks lists the sets per deck.
seedNo
questionNo
allowReversedNo

Output Schema

NameRequiredDescriptionDefault
seedNo
drawnNo
spreadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world profile, so safety is covered. The description adds genuinely useful context in the cost line ('10 credits (Tier 1)') and endpoint path, which help the agent budget calls, but it says nothing about determinism with `seed`, whether reversed cards appear in the output, or how the three persons are mapped to positions.

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 spread summary is front-loaded in one short line, followed by compact bracketed metadata. Nothing is padded, though the group/endpoint/cost lines are boilerplate that could be trimmed if the platform surfaces them elsewhere.

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

Completeness2/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 explained, but for a spread tool with four parameters at 25% coverage the description leaves too much unspecified: no explanation of the card positions/three-person layout, no seeding guidance, and no note on whether `question` is required to get meaningful results.

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 coverage is only 25%: only `art` is documented, leaving `seed`, `question`, and `allowReversed` (which has a default of true) undocumented in both schema and description. The description does not compensate at all — it never mentions seeding for reproducibility, the 500-char question limit, or what allowReversed changes. With three of four parameters carrying no semantics, a low score is warranted.

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 names a specific spread and scope: '6-card three-person love dynamics' for the Rider-Waite-Smith deck. This is clearly distinguishable from siblings like draw_relationship or draw_love, though the verb 'draw' is only implied by the tool name and endpoint 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 Guidelines2/5

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

There is no guidance on when to choose this over the many nearby siblings (draw_relationship, draw_decision, draw_celtic_cross, relational_match_score). No prerequisites, no exclusions, no mention of whether a question is required or optional, which matters given the optional `question` parameter.

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

Deploy Server

Other Tools