Skip to main content
Glama

Suggest belief-compatible remedies

suggest_safe_practice
Read-onlyIdempotent

Returns a short, low-burden practice plan (journaling, an act of service, a reflection) from the evidence ledger and user preferences. It can return no-remedy-needed and does not claim causality. For the planet repertoire (mantra, charity, vrata, gemstone) and screened Lal Kitab remedies, use analyze_remedies.

Input Schema

NameRequiredDescriptionDefault
dateYes
nameNo
timeYes
placeNoCatalogue query or display label when explicit coordinates are supplied
topicYes
detailNobrief omits internal audit sections; full returns the complete protocolbrief
languageNoen
latitudeNo
timezoneNoRequired IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata
longitudeNo
preferencesYes
timezoneOffsetNoOptional fallback offset; derived from timezone and the requested local date when omitted

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
      -  "schemaVersion",
      -  "diagnosis",
      -  "outcome",
      -  "preferences",
      -  "remedyFamilyEligibility",
      -  "eligiblePractices",
      -  "traditionalChartRemedies",
      -  "contraindications",
      -  "followUp"
      -]New value: +[
      +  "schemaVersion",
      +  "diagnosis",
      +  "outcome",
      +  "preferences",
      +  "eligiblePractices",
      +  "traditionalChartRemedies",
      +  "contraindications",
      +  "followUp"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "brief",
      +  "description": "brief omits internal audit sections; full returns the complete protocol",
      +  "enum": [
      +    "brief",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / language
      Added value: +{
      +  "default": "en",
      +  "enum": [
      +    "en",
      +    "te"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "date",
      -  "time",
      -  "topic",
      -  "preferences"
      -]New value: +[
      +  "date",
      +  "time",
      +  "topic",
      +  "preferences"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "career",
      -  "education",
      -  "property",
      -  "relationships",
      -  "spirituality",
      -  "wealth"
      -]New value: +[
      +  "career",
      +  "education",
      +  "property",
      +  "relationships",
      +  "spirituality",
      +  "wealth",
      +  "health",
      +  "children"
      +]
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety bar is largely met structurally. On top of that the description discloses two behaviors the annotations cannot: it may legitimately return no-remedy-needed, and it explicitly does not claim causality — an epistemic constraint that shapes how an agent should present the output. It says little about how the plan is ranked or filtered by burden/cost, which limits it to a 4.

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?

Two sentences, zero filler. The positive scope and output shape come first, the epistemic caveat second, and the sibling hand-off last — exactly the order an agent needs to decide and then call.

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?

An output schema exists, so return values need no prose, and the description correctly focuses on routing, output nature, and limitations. For a 12-parameter tool with a nested preferences object and an anyOf location requirement, the one remaining gap is that the dual location input mode (place label vs. explicit coordinates plus IANA timezone) is never mentioned in prose, relying on schema descriptions instead.

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 only 33% across 12 parameters, so the description carries real weight. It does add meaning for the nested preferences block by tying 'low-burden' and 'belief-compatible' to maximumBurden/maximumCost and beliefMode, but the birth-data parameters (date, time, place vs. latitude/longitude/timezone), topic, language, and detail are left entirely to the schema. That partial compensation is worth a middling 3.

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 pairs a specific verb (returns) with a specific resource (a short, low-burden practice plan drawn from the evidence ledger and user preferences) and even illustrates the categories (journaling, act of service, reflection). Crucially, it names the boundary against the sibling that could be confused with it: planet repertoire and screened Lal Kitab remedies belong to analyze_remedies.

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?

It gives an explicit routing rule to analyze_remedies for mantra/charity/vrata/gemstone and Lal Kitab work, which is exactly the disambiguation an agent needs. It also warns that a no-remedy-needed outcome is possible so the agent doesn't treat an empty result as failure. It stops short of describing prerequisites (e.g., preferences must be supplied), but the alternative path is stated clearly.

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