Skip to main content
Glama

AstroLogics

Get one of my saved charts

get_my_chart
Read-onlyIdempotent

Get a saved birth chart from the signed-in user's AstroLogics account by its id or name (for example "Mom"), with the chart features included in the plan the user already has: planets, houses, the Vimshottari dasha running today (currentDasha) and, where included, antardasha, dasha periods, yogas and divisional charts.

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": {
      "chart": "<chart>"
    },
    "name": "get_my_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartYesThe chart id from list_my_charts, or its name.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.",
      +  "enum": [
      +    "en",
      +    "hi"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is low. The description adds genuinely useful behavior: results are gated by the user's existing plan and enumerate which sections come back (planets, houses, currentDasha, plus optionally antardasha, yogas, divisional charts). It does not say what happens when the id or name is unknown, or whether name lookup can be ambiguous.

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 sentence that front-loads the action, key, and ownership before appending the returned-feature list. The inclusion list is long but each item carries information for an agent deciding whether the response suffices; no filler sentences.

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 correctly compensates by enumerating the returned features and noting plan-based gating. Remaining gaps are behavioral edge cases (missing chart, ambiguous name, partial-plan responses), which are minor for a two-parameter read.

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%, so both parameters are already documented, making 3 the baseline. The description contributes a concrete example of name-based lookup ("Mom"), but ignores the language parameter entirely and adds no detail on case sensitivity or partial matching.

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 (get a saved birth chart) plus the retrieval key (id or name) and the ownership scope (signed-in user's account), which separates it from listing or computing charts. It never names a sibling such as list_my_charts or get_birth_chart, so the differentiation is implicit rather than explicit.

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?

The description implies usage (fetch one already-saved chart, keyed by id or name, subject to the user's plan) and the schema points to list_my_charts as the id source. However, it gives no explicit when-to-use versus when-not guidance, e.g. it never says to use get_birth_chart for a computed chart or list_my_charts to enumerate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources