Jeeva Jyotish

Get a per-lagna placement record

get_placement

Fetch the full reference record for a per-lagna placement (Bhrigu Samhita) by its slug — e.g. 'Sun in the 1st House for Aries Ascendant' — including its component factors, all effects and a source.url citation.

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": {
      "slug": "<slug>"
    },
    "name": "get_placement"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`locale`	No	Response language (default en).

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Describes what the tool returns (factors, effects, source citation) and implies read-only behavior via 'Fetch'. No annotations provided, so description carries the burden; it adequately discloses core behavior but lacks specifics on idempotency or caching.

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?

Single sentence front-loads the purpose and includes examples. Slightly run-on with dashes, but no unnecessary words. Efficient for the information conveyed.

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?

Given the tool's simplicity (2 parameters, no output schema), the description sufficiently explains the return structure and key components. Lacks discussion of error conditions or limitations, but adequate for a straightforward fetch operation.

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?

Provides a concrete example for the slug parameter, adding meaning beyond the schema. However, the locale parameter is not mentioned in the description, and schema coverage is 50%. The description partially compensates for the undocumented slug but does not cover locale.

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?

Clearly states it fetches a full reference record for a per-lagna placement by slug, with specific examples and included components. Distinguishes from sibling tools like 'get_factor' and 'get_yoga' by focusing on placement records.

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?

Implied usage context (fetching a placement record) but no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives like 'lookup_combination' or 'search_effects', leaving the agent to infer appropriateness.

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

All Jeeva Jyotish 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?