Skip to main content
Glama

Удаление логотипа аккаунта

delete_workspace_logo
Destructive

Удаляет логотип рабочего пространства.

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": "delete_workspace_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID рабочего пространства. Взять из workspace://list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether removal is irreversible, whether a default logo is restored, whether admin rights are needed, or how success is reported. With no annotations-level gap to fill beyond the mutation flag, the absence of any extra behavioral context is a clear shortfall.

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?

A single short sentence with no filler, front-loading the action and resource. Its brevity is appropriate for a one-parameter deletion tool, though it verges on under-specification rather than lean design.

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 trivial one-param destructive tool with full schema coverage, no output schema, and annotations that already flag destructiveness, the description is complete enough to call correctly. Only the fallback behavior after deletion (e.g., default logo restored) is left unstated, which is a minor gap.

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 the single parameter workspace_id is documented in the schema, including a pointer to workspace://list for obtaining the ID. The description does not mention the parameter at all, so baseline 3 applies — the schema does all the work.

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 names a specific verb and resource — 'Удаляет логотип рабочего пространства' — so an agent can tell it removes the workspace logo rather than any other workspace artifact. It does not explicitly name upload_workspace_logo as its counterpart, and the title ('логотип аккаунта') slightly conflicts with the description's 'логотип рабочего пространства', but the core action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as upload_workspace_logo (which would replace rather than remove the logo), and no stated prerequisites such as required permissions or workspace ownership. The agent must infer the usage context entirely.

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