Skip to main content
Glama

list_my_organizations

Read-only

Organizations the coach belongs to (owns, manages, or is a member of), with their role in each.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it defines what 'my' means (owner, manager, or member) and discloses that the caller's role in each organization is included in the response, which matters because there is no output schema.

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 front-loaded sentence with the resource first and the qualifying scope immediately after. No redundant restatement of the title and no 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 no-parameter, read-only listing tool whose annotations already confirm it is a safe operation, the definition covers scope and the key returned attribute (role). Minor omissions remain, such as whether pending invitations are excluded (a separate sibling appears to cover those) and whether results are paginated or ordered.

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?

Assessed for consistency with the zero-argument schema, which carries no parameters for the description to explain. The description's breakdown of membership types ('owns, manages, or is a member of') is the main added semantic value.

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 resource (organizations) and precisely defines its scope as the parenthetical '(owns, manages, or is a member of)'. The verb is only implicit via the tool name 'list', and no sibling is named, but the resource is distinct enough that an agent can separate it from list_my_communities or get_my_pending_org_invitations.

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?

Usage is only implied: an agent can infer this is the tool for retrieving the caller's organization memberships with roles, but the description never states when to prefer it or rules out related tools. For a zero-parameter read tool with self-evident scope, that is adequate but not instructive.

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.