Skip to main content
Glama
Sign In

AstralRead

by com.astralread
OverviewDiscussionsAdmin

Ask the AstralRead astrologer

ask_astrologer

Asks the AstralRead astrologer a question about one saved chart of the signed-in user — the same astrologer as on astralread.com: the chart, the current transits and classic astrology and psychology books. Uses one question of the user's AstralRead plan; the answer is also saved in the chart's chat on the site. Not medical, legal or financial advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "ask_astrologer"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the result: en or ru.en
chart_idNochart_id from my_charts; omit for the first (own) chart.
questionYesThe question, in the user's words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=false and destructive=false, and the description usefully adds that a call consumes one question from the user's plan and that the answer is persisted to the chart's chat on the site — real cost and side-effect disclosure beyond the flags. It stops short of stating whether the answer is returned inline in the response or only retrievable later on the site, and gives no latency or failure behavior.

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?

Front-loads the action and packs cost, persistence, answer basis and disclaimer into a compact block. The middle clause listing the astrologer's sources is a slight run-on but earns its place by explaining what the answer is grounded in.

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?

With no output schema, the description does enough for a single-answer tool: it identifies the answer's source basis, that a plan credit is spent, and that the answer is saved. The one gap is the shape of the immediate response (answer text vs. status/reference), which an agent would need to know.

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 description coverage is 100%, so lang, chart_id (including the "omit for the first (own) chart" default) and question are already documented. The description adds only the implicit constraint that chart_id must reference a saved chart of the signed-in user, which is largely restated by the schema.

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?

States a specific verb and resource: it asks the AstralRead astrologer a question about one saved chart belonging to the signed-in user. The scoping ("one saved chart of the signed-in user") distinguishes it from the chart/transit computation siblings, though it never names an alternative tool explicitly.

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?

Implies usage through the quota and disclaimer context but never states when to ask the astrologer versus computing charts, transits or dasha with the siblings. The "Not medical, legal or financial advice" line is a genuine content exclusion, but it constrains question topic rather than tool selection.

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

All AstralRead toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources