Skip to main content
Glama

Porutham: Mahendram

astroway_vedic_compatibility_porutham_mahendra
Read-onlyIdempotent

Mahendra porutham alone: count from the bride's star to the groom's; 4, 7, 10, 13, 16, 19, 22, 25 agree.

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

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.7/5.0
Behavior4/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 safety is covered. The description adds genuinely new operational context: the HTTP endpoint, the required charts, and a 50-credit Tier 3 cost, which matters for a paid computation. It does not discuss response shape, but an output schema exists so that burden is lifted.

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?

The computational rule is front-loaded in a single sentence, followed by compact bracketed metadata for group, endpoint, required params and cost. Nearly every token earns its place; the endpoint string is the weakest element for an agent that only calls the tool.

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?

For a two-chart, single-factor compatibility computation, the description supplies the deciding rule, the required inputs, and the credit cost, and an output schema covers return values. Only the relationship to the aggregate porutham tool is left implicit.

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?

With 60% schema description coverage, the baseline is 3. The description reinforces the required chart1/chart2 and the counting direction (bride to groom), but that directional semantics is already present in the schema's nested chart descriptions, so the added meaning is marginal. The school, fields and precision parameters are left entirely to the schema.

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?

The description names the exact factor computed (Mahendra porutham) and states the actual rule: count from the bride's star to the groom's, with the agreeing counts 4, 7, 10, 13, 16, 19, 22, 25. The word "alone" signals this is a single-factor tool rather than the aggregate porutham sibling, though it never names that sibling explicitly.

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?

"Mahendra porutham alone" implies this is the narrow, single-factor variant to pick when only Mahendra is wanted, but there is no explicit statement of when to prefer it over the full porutham or ashtakoot tools. Usage is inferable rather than stated.

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