Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Lenormand: 36 Houses

astroway_tarot_lenormand_houses
Read-onlyIdempotent

The 36 fixed houses for Grand Tableau interpretation.

[Group: Tarot: Lenormand] [Endpoint: GET /v1/tarot/lenormand/houses] [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_lenormand_houses"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / count / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / count / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / items / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "baseCardName": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "lifeArea": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "position": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "baseCardName": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "lifeArea": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "position": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

B3.4/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 openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational context — cost of 10 credits (Tier 1) and the endpoint — but says nothing about whether this is static reference data requiring no user input, or how large the returned set is.

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 core statement is a single front-loaded sentence with no waste. The bracketed group/endpoint/cost block is boilerplate but functional; it could be trimmed without loss other than the useful cost disclosure.

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?

With an output schema present and annotations covering safety, the description does not need to explain return values. Still, for a reference-lookup tool with zero required parameters, it leaves the agent unsure whether it can be called standalone or must follow a Grand Tableau draw, which is the one piece of context that would most change invocation behavior.

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 coverage is 100% and both optional parameters (fields, precision) are fully documented in the schema itself, so the description carries no parameter burden. It adds no meaning beyond the schema, which is acceptable given the high coverage, but it also gives no hint that these are generic response-shaping parameters rather than query filters.

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 resource — the 36 fixed Lenormand houses used in Grand Tableau interpretation — so an agent can predict the payload. However, it is a noun phrase with no verb (retrieve/return), and it does not distinguish itself from nearby siblings such as astroway_tarot_lenormand_draw_grand_tableau or astroway_tarot_lenormand_cards, which have overlapping topical scope.

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?

The clause 'for Grand Tableau interpretation' implies when this data is useful, but usage is only implied. There is no explicit statement of when to call this versus drawing a Grand Tableau spread, nor whether it must be paired with a draw tool to be meaningful.

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