Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Libra: Cardinal Air

astroway_zodiac_signs_per_sign_deep_zodiac_libra
Read-onlyIdempotent

Retrieve a deep astrological profile for Libra, including partnership dynamics, aesthetic balance, mediation themes, and Venus-ruled traits for interpretation.

Instructions

Partnership, aesthetic balance, mediation. Ruler Venus. I BALANCE.

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

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
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 fully covered. The description adds genuine value by disclosing the cost (10 credits, Tier 1) and the concrete endpoint, but says nothing about content depth or payload size beyond what the output schema provides.

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 keyword line is front-loaded and the metadata tags (group, endpoint, cost) are compact and scannable with no filler. It is efficient, though the keyword style borders on evocative rather than explanatory, so it stops just short of a top score.

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 zero params, full annotation coverage, and an output schema, most of the burden is already handled. The remaining gap is that the description never characterizes what the deep profile actually contains (traits, compatibility, transits, etc.), which would help an agent decide between this and tools like astroway_ai_interpret_placement.

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 no parameter semantics to document; the baseline of 4 applies. The description correctly implies there is nothing to supply for the sign since Libra is baked into the endpoint.

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 name plus the '[Group: Zodiac Signs (Per-Sign Deep)]' tag and '/v1/zodiac/libra' endpoint make it clear this returns a deep per-sign profile for Libra, and the keyword line (partnership, aesthetic balance, mediation, ruler Venus) confirms the subject. There is no explicit verb stating what is returned, but the resource is unambiguous and distinguishable from the sibling sign endpoints.

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?

Nothing states when to reach for this versus the other sign deep-dives or versus natal/chart tools; the only routing signal is implicit in the sign name. The cost line (10 credits, Tier 1) is the sole piece of decision-relevant context, and no alternatives or exclusions are named.

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