Skip to main content
Glama

Sahadeva

by io.github.everyai-com
OverviewDiscussionsAdmin

Get one full-life-report section

get_full_life_report_section
Read-onlyIdempotent

Returns one bounded section of the full report for MCP clients with limited context windows.

Input Schema

NameRequiredDescriptionDefault
dateYes
nameNo
timeYes
placeNoCatalogue query or display label when explicit coordinates are supplied
sectionYes
asOfDateNo
languageNoen
latitudeNo
timezoneNoRequired IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata
longitudeNo
horizonYearsNo
timezoneOffsetNoOptional fallback offset; derived from timezone and the requested local date when omitted
birthTimeAccuracyMinutesNo

Output Schema

NameRequiredDescriptionDefault
dataYes
safetyYes
sectionYes
schemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "place"
+    ]
+  },
+  {
+    "required": [
+      "latitude",
+      "longitude",
+      "timezone"
+    ]
+  }
+]
    • addedInput schema / properties / latitude / maximum
      Added value: +90
    • addedInput schema / properties / latitude / minimum
      Added value: +-90
    • addedInput schema / properties / longitude / maximum
      Added value: +180
    • addedInput schema / properties / longitude / minimum
      Added value: +-180
    • addedInput schema / properties / place / description
      Added value: +"Catalogue query or display label when explicit coordinates are supplied"
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "summary",
-  "life-areas",
-  "placements",
-  "strengths",
-  "vargas",
-  "aspects",
-  "ashtakavarga",
-  "synthesis",
-  "timing",
-  "uncertainty",
-  "evidence",
-  "citations"
-]New value: +[
+  "summary",
+  "life-areas",
+  "placements",
+  "strengths",
+  "vargas",
+  "aspects",
+  "ashtakavarga",
+  "synthesis",
+  "timing",
+  "uncertainty",
+  "evidence",
+  "citations",
+  "yogas",
+  "special-points",
+  "transits"
+]
    • addedInput schema / properties / timezone / description
      Added value: +"Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata"
    • addedInput schema / properties / timezoneOffset / description
      Added value: +"Optional fallback offset; derived from timezone and the requested local date when omitted"
    • addedInput schema / properties / timezoneOffset / maximum
      Added value: +14
    • addedInput schema / properties / timezoneOffset / minimum
      Added value: +-14
    • changedInput schema / required
      Previous value: -[
-  "date",
-  "time",
-  "place",
-  "latitude",
-  "longitude",
-  "timezoneOffset",
-  "section"
-]New value: +[
+  "date",
+  "time",
+  "section"
+]
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "date",
-  "time",
-  "place",
-  "latitude",
-  "longitude",
-  "timezoneOffset",
-  "section"
-]New value: +[
+  "date",
+  "time",
+  "place",
+  "latitude",
+  "longitude",
+  "timezoneOffset",
+  "section"
+]
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that output is 'bounded', which is useful context for context-window management, but says nothing about section sizing, caching, or whether sections are independent across calls.

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?

A single front-loaded sentence with no filler; the resource and its bounding constraint come first. Nothing could be trimmed without losing content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, but the input surface is complex (13 params, anyOf location branching, 23% coverage) and the description addresses none of it. One sentence is inadequate for a tool this compound.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 23% across 13 parameters, so the description must compensate and it does not. It never mentions the mutually exclusive location input (place OR latitude/longitude/timezone), the required date/time/section trio, or what the section enum values denote.

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?

States a specific verb ('Returns') and resource ('one bounded section of the full report'), and the word 'section' plus the enum signals it is the paginated counterpart to generate_full_life_report. It does not explicitly name that sibling, so an agent must infer the relationship from the name alone.

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?

'for MCP clients with limited context windows' implies when to prefer this over the full report, but there is no explicit 'use this instead of generate_full_life_report when...' statement or exclusion. Usage is implied rather than stated.

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

All Sahadeva toolsInspect
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