Sahadeva

Render a shareable birth chart

render_chart

Read-onlyIdempotent

Renders a deterministic birth chart as inline SVG in South Indian (default), North Indian or East Indian style, for the rasi chart or any divisional chart, with the lagna marked, degrees in the rasi chart, and retrograde and combustion flags.

Input Schema

Name	Required	Description	Default
`date`	Yes
`name`	No
`size`	No
`time`	Yes
`place`	No
`style`	No	South Indian (fixed signs), North Indian (fixed houses) or East Indian (Bengal/Odisha) layout	south
`theme`	No		light
`varga`	No	Divisional chart: D1 (rasi), D9 (navamsa), D10 and so on up to D144	D1
`language`	No		en
`latitude`	No
`timezone`	No
`longitude`	No
`timezoneOffset`	No

Output Schema

Name	Required	Description	Default
`svg`	Yes
`style`	No
`varga`	No
`format`	Yes
`safety`	Yes
`mimeType`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 18, 2026

addedInput schema / properties / language

Added value: +{
+  "default": "en",
+  "enum": [
+    "en",
+    "te"
+  ],
+  "type": "string"
+}

addedInput schema / properties / style

Added value: +{
+  "default": "south",
+  "description": "South Indian (fixed signs), North Indian (fixed houses) or East Indian (Bengal/Odisha) layout",
+  "enum": [
+    "south",
+    "north",
+    "east"
+  ],
+  "type": "string"
+}

addedInput schema / properties / theme

Added value: +{
+  "default": "light",
+  "enum": [
+    "light",
+    "dark"
+  ],
+  "type": "string"
+}

addedInput schema / properties / varga

Added value: +{
+  "default": "D1",
+  "description": "Divisional chart: D1 (rasi), D9 (navamsa), D10 and so on up to D144",
+  "type": "string"
+}

addedOutput schema / properties / style

Added value: +{
+  "enum": [
+    "south",
+    "north",
+    "east"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / varga
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 15, 2026

changedInput schema / required

Previous value: -[
-  "name",
-  "date",
-  "time"
-]New value: +[
+  "date",
+  "time"
+]

First observedOct 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare the safe profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context: output is deterministic and returned as inline SVG, and it discloses what the rendering contains. It omits size/pixel constraints and any note about how coordinates vs place resolve.

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?

A single front-loaded sentence with the verb and output format first, then the feature list. Dense but no wasted clauses; the only cost is that the stacked qualifiers make it read more like a spec than guidance.

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?

An output schema exists, so return values need not be re-explained, and the description usefully names the rendered contents. However, with 13 inputs at 15% coverage it never addresses the anyOf location contract (place or lat/lon/timezone) nor input formats, leaving meaningful gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 15% across 13 params, so the description must carry the load. It clarifies style variants and the varga range (D1 rasi through divisional charts), but those are already in the schema, while date/time formats, place vs latitude/longitude/timezone alternative, theme, language, name and size remain unexplained.

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 precise verb (renders) and resource (birth chart) plus the output medium (inline SVG), which cleanly separates it from the analyze_*/calculate_* siblings that produce data rather than a visual. It even enumerates the chart styles and the features baked into the image (lagna, degrees, retrograde/combustion flags).

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?

Usage is only implied: an agent can infer this is the visualization step, but the description never says when to render versus call calculate_south_indian_chart or generate_report_pdf, nor any prerequisite (e.g. an already-computed chart). No exclusions or alternatives are named.

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

All Sahadeva 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.