Skip to main content
Glama

Get White-label Config

astroway_whitelabel_config
Read-onlyIdempotent

Read the authenticated user's branding overrides (logo, colour palette, font, footer text, custom domain). On first access, defaults are seeded.

[Group: White-label] [Endpoint: GET /v1/whitelabel/config] [Cost: 10 credits (Tier 1)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_whitelabel_config"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
updated_atNo
font_familyNo
footer_textNo
custom_domainNo
primary_colorNo
domain_verifiedNo
secondary_colorNo
logo_storage_keyNo
domain_last_checked_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedOutput schema / properties / domain_verified / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / domain_verified / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / font_family / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / font_family / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / primary_color / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / primary_color / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / secondary_color / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / secondary_color / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / updated_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / updated_at / type
      Added value: +[
      +  "string",
      +  "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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower, yet the description still adds two useful facts: that defaults are seeded on first access (an initialization side effect worth flagging) and the per-call credit cost. It stops short of describing response shape or whether seeded defaults persist server-side.

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?

Two short, front-loaded sentences; the important scoping fact (authenticated user's own branding) leads. The bracketed metadata lines (group, endpoint, cost) are useful but slightly clutter the prose.

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?

A simple, parameter-optional read tool with an output schema and full safety annotations needs little more than this. The first-access seeding note covers the one non-obvious behavior; only the relationship to the logo/preview siblings remains unaddressed.

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 100% and both parameters (fields, precision) are fully documented in the schema with examples and rounding guidance. The description adds no meaning beyond that, so the baseline 3 applies rather than a penalty.

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?

States a specific verb and resource ("Read the authenticated user's branding overrides") and enumerates the returned fields (logo, colour palette, font, footer text, custom domain). It is clear what the tool does, but it does not differentiate itself from the closely related siblings astroway_whitelabel_logo and astroway_whitelabel_preview, which overlap with "logo" and general branding inspection.

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?

Usage context is implied (fetch current branding config for the authenticated user) and the 10-credit Tier 1 cost hints at call economy, but there is no explicit when-to-use or when-not-to-use guidance relative to astroway_whitelabel_preview or astroway_whitelabel_logo. The agent must infer the boundary from tool names alone.

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