Skip to main content
Glama

Porutham: Stree Deergham

astroway_vedic_compatibility_porutham_stree_deergha
Read-onlyIdempotent

Stree Deergha porutham alone: count from the bride's star to the groom's; above 13 agrees, above 7 agrees in part.

[Group: Vedic] [Endpoint: POST /v1/vedic/compatibility/porutham/stree-deergha] [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_stree_deergha"
  }
}

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

A4.3/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context beyond that: required chart inputs, a 50-credit Tier 3 cost, and the interpretation thresholds above 13 and above 7. It does not describe error behavior, but the annotations and output schema cover the main safety and return-value concerns.

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 tightly front-loaded: the tool's identity and rule are stated first, followed by compact bracketed metadata for group, endpoint, required parameters, and cost. Every element is relevant to selection or invocation, with no wasted prose.

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?

For a specialized single-factor compatibility tool with an output schema and detailed input schema, the description provides what an agent needs: the factor being computed, the counting direction, interpretation thresholds, required inputs, and cost. Return-value details are appropriately left to the output schema.

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 60%, with five parameters and rich nested descriptions for the chart objects. The description adds directional meaning by stating the count runs from the bride's star to the groom's and that chart1 and chart2 are required. However, it does not clarify the chart1/chart2-to-bride/groom mapping, school selection, or precision/fields behavior beyond what the schema already provides.

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 names the exact compatibility factor, states that it is the Stree Deergha porutham alone rather than a combined score, and explains the core calculation: count from the bride's star to the groom's. The thresholds above 13 and above 7 further specify what this tool evaluates, making it distinguishable from sibling porutham tools.

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 word "alone" clearly signals that this tool should be used when only the Stree Deergha factor is wanted, rather than the full or multi-factor compatibility tools. It does not explicitly name alternatives or state when not to use it, but the context for selection is clear.

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