Skip to main content
Glama

Сведения об аккаунте

get_workspace_details
Read-onlyIdempotent

Рассказывает, что это за аккаунт и что в нём можно владельцу ключа: название, владелец ли он, включены ли AI-отчёты и вход через SSO, сколько папок, опросов и участников, полный список его прав и роль, которая их задаёт (member_role, у владельца null). Половина отказов инструментов — это отсутствующее право, и по этому списку видно заранее, что получится, а что нет. Возможности тарифа — отдельно, в get_workspace_tariff.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID workspace. Взять из workspace://list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered, but the description adds real behavioural context above that bar: the notion that the caller's permission list predicts which other tools will refuse, and the member_role=null edge case for owners. With no output schema, it also carries the burden of describing the returned payload, and it does so field by field.

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?

The description is front-loaded with the answer ('what this account is') before the field inventory, and the tariff pointer is correctly relegated to the end. It is a dense enumeration and one sentence runs long, but every clause carries payload information rather than filler.

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 single-parameter read tool with no output schema, the description is nearly sufficient: it spells out the returned fields and the null-role special case. The only shortfall is the absence of any error/edge behaviour (invalid or inaccessible workspace_id) or note on how the permission list relates to get_workspace_roles.

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 workspace_id already documents its origin ('Взять из workspace://list'), so the schema does all the work. The description adds no extra meaning about the parameter — no format, no error case for an unknown ID — so the baseline of 3 applies.

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 uses a specific verb and resource ('рассказывает, что это за аккаунт') and then enumerates the exact contents: name, owner flag, AI-reports and SSO status, folder/survey/member counts, the full permission list, and the governing member_role (null for the owner). That level of field enumeration lets an agent tell exactly what this tool returns, and the closing sentence routes the tariff question to get_workspace_tariff, so it is distinguishable from at least the closest sibling.

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?

It gives a concrete reason to reach for this tool: 'Половина отказов инструментов — это отсутствующее право', i.e. call this first to see which operations will succeed, and it explicitly excludes tariff data by naming get_workspace_tariff. What's missing is any explicit negative case (e.g. an already-known workspace or a non-owner caller) — the guidance is clear but not exhaustive.

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