Skip to main content
Glama

Porutham: Rajju

astroway_vedic_compatibility_porutham_rajju
Read-onlyIdempotent

Rajju porutham alone: the five rajju (Siro, Kanta, Udara, Kati, Pada) of the two birth stars; the same rajju fails, with the consequence the manuals name. Same function as the factor inside /porutham.

[Group: Vedic] [Endpoint: POST /v1/vedic/compatibility/porutham/rajju] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)]

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": {
      "chart1": "<chart1>",
      "chart2": "<chart2>"
    },
    "name": "astroway_vedic_compatibility_porutham_rajju"
  }
}

Input Schema

NameRequiredDescriptionDefault
chart1Yes
chart2Yes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
schoolNoPorutham school. tamil (default) or kerala. The ten factor tables are the same in both; kerala adds Papasamyam.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
passNo
ruleNo
basisNo
brideNo
groomNo
scoreNo
detailNo
factorNo
methodNo
schoolNo
sourceNo
verdictNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / school / description
      Previous value: -"Porutham school. tamil (default) or kerala; they differ on Dinam, Stree Deergham, Rasi and on which factors are essential."New value: +"Porutham school. tamil (default) or kerala. The ten factor tables are the same in both; kerala adds Papasamyam."
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the failure semantics ('the same rajju fails') plus endpoint and credit cost, which is genuine added context, but 'with the consequence the manuals name' is evasive rather than informative about what the output asserts.

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 factor name and its rule, then the metadata block. It is appropriately short, with only the vague 'consequence the manuals name' clause costing clarity.

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 an output schema present, return values need no explanation, and annotations cover the safety profile. Purpose, cost, endpoint and required inputs are all available between description, metadata and schema, leaving only the school parameter's effect on results unaddressed at the description level.

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 60% and the nested birth-data schema is itself heavily documented (timezone vs timezoneOffset, date/time formats, houseSystem letters), so the schema carries most of the burden. The description contributes only 'the two birth stars' and never mentions the groom/bride direction or the school parameter, so it adds little beyond structured data.

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?

Names the exact factor (Rajju), enumerates the five rajju categories (Siro, Kanta, Udara, Kati, Pada), and states the rule (same rajju fails). The phrase 'alone' plus 'Same function as the factor inside /porutham' cleanly separates it from the aggregate sibling.

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?

The 'alone' framing and the pointer to the factor inside /porutham make it clear this is the single-factor call rather than the full porutham. It does not explicitly say when to prefer the aggregate or what else the caller might need, but the cost line (50 credits, Tier 3) gives a practical basis for choosing the cheaper single factor.

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