Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

RWS: 16 Court Cards

astroway_tarot_rider_waite_courts
Read-onlyIdempotent

Retrieve all 16 Rider-Waite-Smith court cards (Page, Knight, Queen, King across four suits) for tarot readings or study.

Instructions

The 16 Court cards (Page, Knight, Queen, King × 4 suits).

[Group: Tarot: Rider-Waite-Smith] [Endpoint: GET /v1/tarot/rider-waite/courts] [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_courts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful cost and endpoint metadata, but does not explain the return behavior or confirm that the result is static reference data.

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

Conciseness5/5

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

The description is front-loaded with the core resource definition and uses compact bracketed metadata for group, endpoint, and cost. There is no redundant or wasted prose.

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

Completeness4/5

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

For a simple parameterless reference endpoint with an output schema and rich annotations, the description is nearly complete. The main missing element is explicit routing guidance relative to nearby tarot tools.

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?

The tool has zero parameters, so there are no parameter semantics for the description to clarify. The empty input schema is consistent with a parameterless listing operation.

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 clearly identifies the resource as the 16 Court cards and enumerates the ranks and suit structure. It distinguishes the subset from broader tarot tools like 'cards', 'majors', and 'minors', though it does not use an explicit verb such as 'list' or 'return'.

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 use this tool versus related siblings such as astroway_tarot_rider_waite_cards, astroway_tarot_rider_waite_majors, or astroway_tarot_rider_waite_minors. Usage is only implied by the resource name.

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