Astro Agents - deterministic Western + Vedic astrology

Catalog (free)

astro_catalog

Read-onlyIdempotent

List every astrology tool with its price, input schema and an example request. Free; call it first to pick the right tool.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`calls`	Yes	The $0.01-0.02 tools: MCP tool name, price, REST route, what it computes and an example request (input schemas are in tools/list).
`payment`	No	Free calls, payment protocols (x402, MPP) and networks.
`premium`	Yes	The full-chart tools, same fields as 'calls'.
`service`	Yes	Service name.
`support`	No	Contact, documentation and policies.
`tagline`	No	One-line summary of the service.
`discovery`	No	Discovery documents: OpenAPI, MCP server card, A2A agent card.
`start_here`	No	Which tool to call first for common questions.
`engine_version`	No	Calculation engine version.
`free_endpoints`	No	Endpoints that are always free (catalog, verify, health).
`why_use_this_instead_of_computing_it_yourself`	No	Reasons to prefer these tools over computing a chart yourself.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / properties / calls / description

Previous value: -"The $0.01-0.02 tools: name, price, REST route, input schema and an example request."New value: +"The $0.01-0.02 tools: MCP tool name, price, REST route, what it computes and an example request (input schemas are in tools/list)."

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calls": {
+      "description": "The $0.01-0.02 tools: name, price, REST route, input schema and an example request.",
+      "type": "array"
+    },
+    "discovery": {
+      "description": "Discovery documents: OpenAPI, MCP server card, A2A agent card.",
+      "type": "object"
+    },
+    "engine_version": {
+      "description": "Calculation engine version.",
+      "type": "string"
+    },
+    "free_endpoints": {
+      "description": "Endpoints that are always free (catalog, verify, health).",
+      "type": "object"
+    },
+    "payment": {
+      "description": "Free calls, payment protocols (x402, MPP) and networks.",
+      "type": "object"
+    },
+    "premium": {
+      "description": "The full-chart tools, same fields as 'calls'.",
+      "type": "array"
+    },
+    "service": {
+      "description": "Service name.",
+      "type": "string"
+    },
+    "start_here": {
+      "description": "Which tool to call first for common questions.",
+      "type": "string"
+    },
+    "support": {
+      "description": "Contact, documentation and policies.",
+      "type": "object"
+    },
+    "tagline": {
+      "description": "One-line summary of the service.",
+      "type": "string"
+    },
+    "why_use_this_instead_of_computing_it_yourself": {
+      "description": "Reasons to prefer these tools over computing a chart yourself.",
+      "type": "array"
+    }
+  },
+  "required": [
+    "service",
+    "calls",
+    "premium"
+  ],
+  "type": "object"
+}

First observedOct 3, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description adds the cost signal ("Free"), which annotations do not express, but its listing of returned fields largely duplicates the existing output schema rather than disclosing new behavior.

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?

Two short sentences, both front-loaded with the highest-value information (what you get, then when to call it). No filler or redundancy.

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

Completeness5/5

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

A zero-parameter, read-only discovery tool with an output schema that already defines the return shape. The description gives the agent everything it needs to decide to call it and expect the catalog contents.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. Schema coverage is 100%, and no invocation arguments need explanation.

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

Purpose5/5

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

States a specific verb (List) and resource (every astrology tool) and details what each entry contains: price, input schema, and example request. That is clearly distinguishable from all listed siblings, which are individual computation tools rather than a catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call it first to pick the right tool" gives explicit ordering guidance for tool selection, which is exactly the agent-facing decision this tool supports. It stops short of naming conditions where it should be skipped, but for a discovery entry point that is a minor omission.

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

All Astro Agents - deterministic Western + Vedic astrology tools Inspect

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.