Skip to main content
Glama

Upload White-label Logo

astroway_whitelabel_logo
Read-onlyIdempotent

Upload a logo as a base64 data URL (data:image/<png|jpeg|svg+xml|webp>;base64,...). Maximum 512 KB. Replaces any prior logo and deletes the old file from storage.

[Group: White-label] [Endpoint: POST /v1/whitelabel/logo] [Required: data_url] [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": {
      "data_url": "<data_url>"
    },
    "name": "astroway_whitelabel_logo"
  }
}

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.
data_urlYes
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
logo_urlNo
mime_typeNo
byte_lengthNo
logo_storage_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedOutput schema / properties / byte_length / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / byte_length / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / logo_storage_key / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / logo_storage_key / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / logo_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / logo_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / mime_type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / mime_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, yet the description says the call uploads a file, 'Replaces any prior logo and deletes the old file from storage' — a state-mutating, destructive operation. The description's behavioral claims directly conflict with the supplied annotations, leaving the agent with contradictory safety signals.

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?

A single dense sentence plus short bracketed metadata lines; the format constraint, size cap, and replacement side effect are all front-loaded with no filler.

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?

Format, size limit, and side effects are covered and an output schema exists so return values need no explanation. But the stray `fields`/`precision` response-shaping parameters go unaddressed, and the fundamental accuracy problem — that this is a write/delete operation described under readOnly annotations — leaves the definition misleading about its own risk profile.

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 coverage is 67% and data_url has only a regex, no description; the prose adds genuine value there by naming the accepted image types and the 512 KB ceiling, which the schema does not express. However, the other two parameters (`fields` and `precision`) are a surprising generic compact-mode pair for an upload tool and are not mentioned at all, so their relevance is left unexplained.

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 opens with a specific verb and resource ('Upload a logo') and immediately specifies the accepted encoding ('base64 data URL' with the allowed MIME types). It is clearly distinguishable from the other whitelabel siblings (config, domain_verify, preview), none of which handle logo assets.

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 '[Group: White-label]' tag plus the replacement semantics imply this is the configuration-time logo setter, but there is no explicit statement of when an agent should call this instead of, say, astroway_whitelabel_config or astroway_whitelabel_preview. Usage is inferable rather than stated.

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