Skip to main content
Glama
intellecat

astrology-mcp

by intellecat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.8

  • Disambiguation5/5

    Each tool has a clearly distinct purpose: one calculates a natal chart, the other converts a location to coordinates for input; no ambiguity.

    Naming Consistency5/5

    Both tools follow the 'astrology_verb_noun' pattern consistently, making the naming predictable and clear.

    Tool Count3/5

    Two tools is minimal for the domain of astrology; while the server may be scoped narrowly, a typical user might expect additional tools like transit or synastry calculations, making it borderline.

    Completeness4/5

    The server covers the essential steps for natal chart calculation (coordinates + chart), but lacks tools for interpretation, aspects analysis, or other astrological functions, leaving minor gaps.

  • Average 4.1/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is passing

  • This repository is licensed under AGPL 3.0.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior3/5

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

    Annotations already indicate idempotent and read-only behavior. The description adds no contradictory information but also does not elaborate on aspects like input validation, potential errors, or calculation caveats. It is adequate but minimal.

    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 description front-loads the main action and uses a bulleted list for return values. It is informative but slightly verbose; could be trimmed without losing content.

    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?

    Given the complexity of natal chart calculation and no output schema, the description provides a solid overview of what is returned. It covers planetary positions, houses, angles, and aspects, but could specify aspect types or degree precision.

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

    Parameters4/5

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

    Despite 0% schema description coverage at the top level, the description adds meaning for the main parameters (datetime, location, house system). It clarifies location can be coordinates or city string, and house system is configurable. This compensates for missing schema descriptions.

    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 clearly states the tool calculates a natal chart based on date, time, and location, and lists specific outputs (planetary positions, houses, angles, aspects). It distinguishes from the sibling tool astrology_get_coordinates, which is for coordinate lookup.

    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?

    The description does not provide explicit guidance on when to use this tool versus alternatives. It mentions support for multiple house systems but lacks context about when not to use or prerequisites.

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

  • Behavior4/5

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

    The description adds information beyond annotations (readOnlyHint, idempotentHint) by specifying the geocoding service (OpenStreetMap). It does not contradict annotations. A score of 4 reflects that while annotations already indicate safety, the description provides useful context about the external dependency.

    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 two sentences with no wasted words. The first sentence states the core action, and the second provides the use case. It is front-loaded and gets straight to the point.

    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?

    Given the simplicity of this tool (1 parameter, no output schema), the description adequately covers what it does and why it is used. However, it could be slightly more explicit about the return format (e.g., 'returns latitude and longitude as numbers'). Still, the agent can infer from the name and use case.

    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?

    The input schema already provides 100% description coverage for the single parameter 'location', including the format 'City, Country'. The description restates the conversion purpose but does not add significant new parameter semantics beyond the schema. Baseline 3 is appropriate.

    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 clearly states the verb ('Convert'), resource ('location string'), and output ('geographic coordinates'). It also mentions the specific service (OpenStreetMap geocoding) and distinguishes from the sibling tool 'astrology_calculate_natal_chart' by describing the prerequisite use case.

    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 description explains when to use this tool ('before calculating a natal chart when only the city name is known'), which provides clear context. However, it does not explicitly state when not to use it or mention alternatives, though the sibling tool is the only alternative.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

astrology-mcp MCP server

Copy to your README.md:

Score Badge

astrology-mcp MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/intellecat/astrology-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server