Skip to main content
Glama

AstroWay Hellenistic and traditional

Via Combusta Check

astroway_horary_via_combusta
Read-onlyIdempotent

Check if the Moon or ASC is in the Via Combusta (15° Libra – 15° Scorpio), a classical prohibition in horary.

[Group: Horary] [Endpoint: POST /v1/horary/via-combusta] [Required: moonLongitude] [Cost: 10 credits (Tier 1)]

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": {
      "moonLongitude": "<moonLongitude>"
    },
    "name": "astroway_horary_via_combusta"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
moonLongitudeYes

Output Schema

NameRequiredDescriptionDefault
warningNo
moonSignNo
ascLongitudeNo
moonLongitudeNo
ascViaCombustaNo
moonViaCombustaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / properties / moonLongitude / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / moonLongitude / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / ascLongitude / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / ascLongitude / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / ascViaCombusta / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / ascViaCombusta / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / moonLongitude / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / moonLongitude / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / moonSign / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / moonSign / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / moonViaCombusta / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / moonViaCombusta / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description's added value is the doctrinal meaning of the result and the cost ('10 credits (Tier 1)'), which is genuinely useful for an agent budgeting calls. It stops short of describing what the response contains, but an output schema exists to cover that.

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?

One substantive sentence front-loads the definition and its significance, followed by a compact bracketed metadata block. The endpoint and group lines are marginal for an agent, but the cost line earns its place.

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 single-test, single-required-parameter tool with an output schema, the description supplies the domain definition, the interpretive stakes, and the price. The remaining gap is the ASC handling and longitude units, which the schema does not fill either.

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 two compact-mode parameters are documented in the schema at 67% coverage, so the schema carries most of the burden. However, the sole required parameter moonLongitude has no schema description, and the description only repeats that it is required without giving units, coordinate frame, or explaining why only Moon longitude is taken when the text claims to also test the ASC.

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 gives a specific verb ('Check') and a precise resource with its defining boundaries (Via Combusta = 15° Libra – 15° Scorpio), plus what is being tested (Moon or ASC). It is clearly distinguishable from the void-of-course siblings by name, though it never states that distinction 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?

Calling it 'a classical prohibition in horary' implies when the check matters, but there is no explicit statement of when to call this versus astroway_horary_moon_voc, astroway_horary_diagnostics, or astroway_horary_horary, and no guidance on what to do with a positive result.

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