AstroCalc: Vedic astrology

My saved family kundlis

my_profiles

Read-onlyIdempotent

List the people whose kundlis the user has saved on AstroCalc (themselves, parents, partner, children, friends): name, gender, birth place, Moon sign, when it was saved, and an id. Use when the user talks about themselves or a family member by name or relation ('my mother', 'my son') and a saved kundli may exist, or asks who is saved. Read-only. Only for people saved on the user's AstroCalc account (needs a free AstroCalc sign-in); birth details typed in the chat work without sign-in in free_kundli, kundli_milan, explain_dasha, full_chart and life_timeline.

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": "my_profiles"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the text fields: 'en' (English, default) or 'hi' (Hindi).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description echoes the read-only nature while adding genuinely new context: an account sign-in requirement and the constraint that only saved people are returned. It stops short of describing edge cases (empty list, what id can be used for, ordering of results), which keeps it below 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?

Front-loaded with the resource and returned fields, then the when-to-use and the exclusion. It is dense but long — the tail list of five sibling tools is useful routing yet slightly heavy for one description; still, nearly every clause earns its place.

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?

There is no output schema, and the description compensates by naming the fields returned and the account scope. Combined with the sign-in prerequisite and the sibling routing, an agent has everything needed to decide whether to call it and how to interpret results.

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 coverage is 100% with a single enum (lang en/hi) fully documented in the schema, so the schema carries the burden. The description never mentions the lang parameter or whether returned names/localization switch with it, adding no meaning beyond the schema. Baseline 3 applies.

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 and resource ('List the people whose kundlis the user has saved') and even enumerates the returned fields (name, gender, birth place, Moon sign, saved time, id). That scope cleanly separates it from siblings like my_kundli (one chart) and free_kundli (unsaved input), so an agent can pick it without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit triggers ('user talks about themselves or a family member by name or relation', 'asks who is saved') and an explicit negative boundary: 'Only for people saved on the user's AstroCalc account (needs a free AstroCalc sign-in)'. It then names the alternative path for chat-typed birth details (free_kundli, kundli_milan, explain_dasha, full_chart, life_timeline), which is exactly the routing an agent needs.

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

All AstroCalc: 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.

Resources

Need Help?