Skip to main content
Glama

List my groups

list_my_groups
Read-onlyIdempotent

List groups that grant access to the signed-in user in the active vault.

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_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size. Defaults to 20.
queryNoOptional search text.
cursorNoOpaque cursor returned by the previous page.

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds useful scoping context (results are limited to the signed-in user's access and the active vault), but says nothing about pagination behavior or ordering beyond what the schema's limit/cursor fields imply.

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 scope constraint in the right place and zero filler. Nothing is repeated from the title and no sentence fails to earn its place.

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?

With an output schema present and all three parameters documented in the schema, the description only needs to establish scope, which it does. The remaining minor gap is that pagination is never acknowledged in prose, but the cursor/limit fields make the pattern self-evident.

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%, with limit, query and cursor each documented inline (defaults, max length, opaque-cursor semantics). The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 states a specific verb and resource ('List groups') plus the exact scope: groups that grant access to the signed-in user within the active vault. An agent can immediately tell this is a personal, vault-scoped listing rather than a general group search. It stops short of naming how it differs from sibling listers such as list_my_skills or list_collections, so it is clear but not fully differentiated.

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: the phrase 'grant access to the signed-in user in the active vault' signals when this listing is relevant, but there is no explicit when-to-use/when-not-to-use statement and no alternative tool is named for broader or admin-level group queries. An agent can infer the context but receives no routing guidance.

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