AstroLogics

Save a chart to my account

save_chart

Idempotent

Save a new birth chart to the signed-in user's AstroLogics account so it appears in their saved charts on the website and app. Only call this when the user asks to save a chart. Saving the same birth details again returns the existing chart.

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": {
      "name": "<name>",
      "date": "<date>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "save_chart"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Birth date, YYYY-MM-DD.
`name`	Yes	Name for the chart, for example "Priya" or "Mom".
`time`	No	Local birth time, HH:MM. Defaults to 12:00 if unknown.
`latitude`	Yes	Birth latitude in decimal degrees.
`longitude`	Yes	Birth longitude in decimal degrees.
`place_name`	No	Birth place name as the user gave it.
`relationship`	No	Optional relationship to the user, for example "self", "spouse", "mother".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=true and openWorld=false. The description earns credit for making the idempotency concrete — 'Saving the same birth details again returns the existing chart' tells the agent no duplicate is created and what the repeat call yields — and it implies the signed-in account context. It does not cover failure modes such as missing required birth data or rate limits.

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?

Three short sentences: purpose and persistence effect first, then the call condition, then the dedupe behavior. No filler and nothing buried.

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?

For a mutation tool with seven params and no output schema, the description covers account scope, user-facing effect, trigger condition, and idempotent return behavior. The main remaining gap is what the call gives back (a chart identifier or the existing chart object), which an agent would want when chaining calls.

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%, with every one of the seven parameters documented in the schema itself, including defaults for time. The description adds no parameter-level meaning beyond that, so the 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?

The description states a specific verb and resource ('save a new birth chart') plus the concrete effect ('appears in their saved charts on the website and app'). That is enough to separate it from the read-oriented siblings like get_my_chart and list_my_charts without opening a schema.

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?

'Only call this when the user asks to save a chart' gives an explicit trigger and an implicit exclusion for exploratory or retrieval requests. It stops short of naming a concrete alternative (e.g. list_my_charts for viewing saved charts), so it is clear context rather than full when/when-not routing.

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

All AstroLogics 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?