Skip to main content
Glama

AstroWay Core astrology

Translate (astro-aware)

astroway_content_localization_translate_astro
Read-onlyIdempotent

Translate one text into any of 21 languages with astrology-domain glossary pinning. Source defaults to English; pass source_lang to override. Credits: 15 + ceil(chars/40). Max 3000 chars.

[Group: Content Localization] [Endpoint: POST /v1/translate/astro] [Required: text, target_lang] [Cost: 16 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": {
      "text": "<text>",
      "target_lang": "<target_lang>"
    },
    "name": "astroway_content_localization_translate_astro"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
domainNo
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.
source_langNo
target_langYes

Output Schema

NameRequiredDescriptionDefault
charsNo
domainNo
creditsNo
providerNo
translatedNo
source_langNo
target_langNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedOutput schema / properties / chars / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / chars / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / credits / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / credits / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / domain / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / domain / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / provider / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / provider / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / source_lang / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / source_lang / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / target_lang / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / target_lang / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / translated / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / translated / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds things annotations cannot carry: a cost formula (15 + ceil(chars/40)), the 3000-char ceiling, and glossary pinning behavior. The stated [Cost: 16 credits (Tier 1)] is consistent with the formula at short lengths. It does not mention rate limits or what happens at the char limit.

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?

Front-loaded with the core behavior, then constraints, then metadata blocks. Every sentence carries information; the bracketed [Group]/[Endpoint]/[Required]/[Cost] lines are boilerplate but short and scannable.

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

Completeness3/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 explanation, and the cost/size/defaults are covered. The gap is the domain parameter: for a tool whose selling point is domain glossary pinning, not explaining which domain to pick for which content is a real omission. The 21-vs-20 language count also weakens confidence.

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 description coverage is 33%, and the description covers only text (max 3000) and source_lang (defaults to English, pass to override). The domain enum (vedic/western/tarot/numerology/hd/marketing/generic) — the parameter that actually drives the 'astro-aware' glossary behavior — is left completely unexplained, as are fields and precision.

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?

"Translate one text into any of 21 languages with astrology-domain glossary pinning" gives a specific verb, resource, and differentiator (single text vs. the translate_batch sibling). The 'astro-aware' qualifier is explained via glossary pinning rather than left as jargon. Minor defect: the schema enum lists 20 languages, not 21.

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?

"one text" implies the batch sibling is the alternative for multiple strings, but translate_batch is never named, and there is no explicit when-not-to-use guidance. The source_lang override note is the only real usage instruction. Adequate but relies on inference.

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