Skip to main content
Glama
Sign In
Asterwise

Asterwise

Official
by asterwise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Lal Kitab Remedies

asterwise_get_lal_kitab_remedies
Read-onlyIdempotent

Retrieves Lal Kitab totkas for stressed planets from BirthData, showing priority tiers and actions like remedy, donation, keep, or avoid.

Instructions

Lists Lal Kitab style totkas per stressed planet from BirthData with priority tiers and typed action rows (remedy, donation, keep, avoid).

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_lal_kitab_chart — see chart before applying totkas. AFTER: None.

INPUT CONTRACT: BirthData only.

DO NOT CONFUSE WITH: asterwise_get_remedies — mantra/gem prescriptions, not Lal Kitab totkas. asterwise_get_gemstone_recommendations — classical Ratna focus, not household remedies.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-lal-kitab-remedies/

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": {
      "birth": "<birth>"
    },
    "name": "asterwise_get_lal_kitab_remedies"
  }
}

Input Schema

NameRequiredDescriptionDefault
birthYesBirth data for a single person.
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already signal readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the baseline safety profile is covered. The description adds useful behavioral context beyond annotations: it lists per-planet stressed analysis, priority tiers, specific action row categories (remedy, donation, keep, avoid), and points to the output/error contract.

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?

The description is front-loaded with the core purpose, then organized into compact WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE WITH sections. Each section earns its place, and there is no redundancy with annotations or schema.

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?

The tool has an output schema, so return-value details are already covered. The description supplies workflow context, alternative tool routing, input contract, and a link to the full output/error contract, making it complete for an agent to decide when and how to call it.

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%, so all parameters are already documented in the input schema. The description adds only the input contract 'BirthData only', which is useful but does not provide any additional meaning beyond the schema; baseline 3 is appropriate.

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 opens with a specific verb ('Lists') and a clear resource ('Lal Kitab style totkas per stressed planet'), and specifies the output shape (priority tiers and typed action rows). It also explicitly distinguishes itself from asterwise_get_remedies and asterwise_get_gemstone_recommendations, so an agent can select it correctly 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?

The WORKFLOW section gives a concrete before-step ('asterwise_get_lal_kitab_chart') and an explicit AFTER: None, and the DO NOT CONFUSE WITH section names alternatives and their differentiating focus. This makes when-to-use and when-not-to-use unambiguous.

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

Deploy Server

Other Tools