Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_docsA

Search the DivineAPI docs by keyword and return the matching endpoint cards.

Case-insensitive token scan over every endpoint reference card. Cards that match more of the query's tokens rank first. Returns up to limit whole cards (path, summary, params, returns). Use this when you know roughly what you want ("auspicious timings", "natal wheel", "love compatibility") but not the exact path.

get_endpointA

Return the full reference card for one endpoint path.

Give an exact path such as /indian-api/v1/auspicious-timings. If the path is not an exact match, the closest single endpoint (substring on the last path segment) is returned, otherwise a short "did you mean..." list of candidates. The card lists the host, summary, params (with * for required and example values), and the top-level response fields (returns: line).

list_endpointsA

List endpoint paths with their hosts, optionally filtered by category.

With no argument, lists every endpoint as "path [host]" lines. Pass a category substring (case-insensitive) to filter, e.g. "Indian", "Western", "Numerology", "PDF", "Horoscope", "Lifestyle", or "Calculators".

get_playbookA

Return the global DivineAPI usage rules (the docs-pack header).

Covers authentication (Bearer token + api_key form field), error semantics per host, the standard birth params, horoscope selectors, field formats, house systems, SDK installs, the MCP server URLs, and a "what not to do" list of common mistakes. Read this before constructing any request.

get_exampleA

Return a real captured example response body for an endpoint path.

Uses the bundled examples (with a version-agnostic slug fallback, so an example captured at /api/v2/x also answers for /api/v3/x). If no example was captured for the path, points you to the card's returns: line instead.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_endpoint returns reference cards, get_example returns example responses, get_playbook returns global rules, list_endpoints lists paths, and search_docs searches by keyword. There is no overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_endpoint, get_example, get_playbook, list_endpoints, search_docs. The naming is predictable and uniform.

Tool Count5/5

With 5 tools, the server is well-scoped for its purpose of serving API documentation. It provides essential functions for retrieving endpoint details, examples, listing, searching, and understanding rules without being excessive or insufficient.

Completeness5/5

The tool set covers all key documentation activities: listing endpoints, searching by keyword, retrieving detailed reference cards, accessing example responses, and obtaining usage rules. There are no obvious missing features for the domain.

Maintenance

ActivitySlowing
ResponsivenessNo issues