Skip to main content
Glama

我的组织树

gwl_list_my_orgs
Read-onlyIdempotent

Lists organizations you belong to or own, including their visible groups, so you can review the hierarchy and choose the right organization ID for group details or blacklist tools.

Instructions

返回我加入/拥有的组织,组织为顶层、下辖我可见的组(groups 数组)。 适合先看清层级关系,再决定用哪个 cid 去调用组类详情或黑名单类工具。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so safety is covered. The description adds that only organizations the caller has joined or owns are returned and that groups are scoped to what the caller can see, which is genuine behavioral context, but it does not discuss permissions, rate limits or result volume.

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 sentences, with the returned structure front-loaded and the follow-up guidance second. No filler, though the closing clause about cid-driven tool selection is only indirectly relevant to this specific call.

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 zero-argument read tool with an output schema needs little more than scope and hierarchy semantics, both of which are provided. The chaining hint covers the main downstream ambiguity, leaving only minor gaps around visibility rules.

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?

The tool takes zero parameters, which normally warrants a baseline of 4, but the description spends its second sentence on a 'cid' concept that is not an input here — useful for chaining yet not parameter semantics for this call. The schema has nothing to explain, so the description neither compensates nor detracts much.

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 ('返回我加入/拥有的组织') and clarifies the shape of the result: top-level organizations each containing a visible 'groups' array. This distinguishes it from the flat class/document list siblings, though it never names an alternative tool explicitly.

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 states a clear use sequence: call this first to understand the hierarchy, then take a cid from the result to invoke group-detail or blacklist tools. There is no explicit 'do not use when' clause, but the intended entry-point role is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.