Skip to main content
Glama

Загрузка логотипа аккаунта

upload_workspace_logo
Destructive

Загружает логотип рабочего пространства по ссылке или из base64. Логотип подставляется во все опросы, отчёты и PDF пространства. Укажите ровно один способ: url или file_base64. url — публичная ссылка на сам файл логотипа: сервер скачает его к себе; это не адрес чужого API.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "upload_workspace_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoПубличная http(s) ссылка на файл логотипа.
filenameNoИмя файла — используется при загрузке из base64 (необязательно).
file_base64NoСодержимое файла в base64 (допускается префикс data:...;base64,).
workspace_idYesID рабочего пространства. Взять из workspace://list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, and the description adds genuinely new behavioral context: the logo propagates into all surveys, reports and PDFs of the workspace, and the server itself fetches the URL. It omits that an existing logo is replaced, along with any format/size limits or permission requirements — relevant gaps for a destructive mutation.

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?

Three short sentences with no padding: purpose first, downstream effect second, input constraint third. The defensive URL clarification is worth its space because it prevents a concrete failure mode.

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?

With no output schema and a destructive, non-idempotent annotation profile, the description should state that an existing logo is overwritten and what a successful call returns. It covers propagation and input selection well, but replacement semantics and acceptance constraints (formats, dimensions, size) are missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by adding the mutual-exclusivity constraint between url and file_base64 and by spelling out that url must point to the file itself, not to an API. It adds no guidance on filename fallback when using base64 or on data-URI prefixes beyond what the schema already states.

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?

States a specific verb and resource ("Загружает логотип рабочего пространства") plus both supported input modes (URL or base64), which cleanly separates it from delete_workspace_logo and from the quiz-media upload siblings by resource scope. An agent knows exactly what the call does without opening the schema.

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?

Gives an explicit invocation rule — "Укажите ровно один способ: url или file_base64" — and pre-empts the common mistake of passing an API endpoint instead of a direct file link ("это не адрес чужого API"). It does not discuss when to prefer this over update_workspace_branding or when removal via delete_workspace_logo is the right call, so usage relative to alternatives is left implicit.

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