Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Taurus: Fixed Earth

astroway_zodiac_signs_per_sign_deep_zodiac_taurus
Read-onlyIdempotent

Retrieve an in-depth astrological profile of Taurus, covering Venus rulership, stability, and sensory themes for per-sign zodiac insights.

Instructions

Embodied stability, sensory wealth. Ruler Venus. I HAVE.

[Group: Zodiac Signs (Per-Sign Deep)] [Endpoint: GET /v1/zodiac/taurus] [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_zodiac_signs_per_sign_deep_zodiac_taurus"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
signNo
cohortNo
decansNo
sourceNo
degreeRangeNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world). The description adds genuinely useful context beyond them: it names the endpoint and discloses a cost of 10 credits (Tier 1), which an agent needs for budgeting calls. It does not state that output is static/cached reference content, keeping it short of a 5.

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?

Very short and front-loaded, and the bracketed metadata lines are compact and scannable rather than padded. The thematic opener is stylistic rather than informative, which costs a little on efficiency, but nothing is redundant.

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, the description need not explain return fields, and annotations handle safety. What is missing is the essential framing that this is a static, no-input reference lookup returning a fixed Taurus profile — an agent must deduce that from the empty schema. Adequate but with a clear gap.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The endpoint line correctly signals the sign is baked into the path rather than supplied as an argument.

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

Purpose3/5

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

The description gives evocative keywords rather than a statement of function: 'Embodied stability, sensory wealth. Ruler Venus. I HAVE.' An agent can infer this is a static reference entry for Taurus from the name, title, and '[Group: Zodiac Signs (Per-Sign Deep)]' line, but the description itself never says it returns a per-sign astrological profile. Purpose is implied, not 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?

No when-to-use, when-not-to-use, or alternative is named. With eleven sibling per-sign tools and many competing zodiac/interpretation tools, the definition offers no routing guidance about when a Taurus deep-dive is the right call versus a natal chart or a general horoscope.

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