Skip to main content
Glama

group_list

Query Operaton groups by ID, name, type, or member user ID and return detailed group records for each match. Use filters, sorting, and pagination to find relevant groups.

Instructions

Query Operaton groups by id, name, type, or member user ID. Returns group details for each matching group.

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

Input Schema

NameRequiredDescriptionDefault
idNo
idInNo
nameNo
typeNo
memberNo
sortByNo
nameLikeNo
sortOrderNo
maxResultsNo
firstResultNo
memberOfTenantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.3.0
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / idIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / member
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / memberOfTenant
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it only discloses that matching groups' details are returned. It is silent on pagination defaults and limits (maxResults, firstResult exist in the schema), sort defaults (sortBy/sortOrder), whether zero matches yields an empty list or an error, and on any permission requirements. The one useful behavioral statement is the confirmation that results are per-match group details rather than a count.

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 short sentences with the filtering capability front-loaded before the return-value note. There is no filler or redundancy. It is efficient, though the tightness comes partly from omitting information an agent actually needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, fully-undocumented, annotation-free list tool with no output schema, the definition is too thin. Pagination, sorting, and the tenant/member scoping parameters are all unaddressed, leaving an agent unable to call it confidently beyond simple id/name lookups.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 11 parameters, so the description would need to compensate and does so only partially: it covers id, name, type and member but leaves idIn, nameLike, sortBy, sortOrder, maxResults, firstResult and memberOfTenant entirely undefined. No formats, allowed values (e.g. group type enumeration), or matching semantics (exact vs pattern for nameLike, case sensitivity) are given. This is a substantial gap on a high-parameter-count tool.

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 ('Query Operaton groups') plus the four filtering axes it supports and the fact that it returns group details. It is clearly distinguishable from siblings like group_create, group_delete, group_addMember and group_removeMember. It stops short of a 5 because it never frames the operation as a list/search-with-pagination tool, despite the presence of sortBy/maxResults/firstResult in the schema.

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?

It names four filter keys but gives no when-to-use guidance relative to alternatives, no statement about which filters can be combined, and no indication of whether filters are optional or how to enumerate all groups. There are no exclusions or prerequisites at all, so an agent must infer usage entirely from the schema.

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

Deploy Server

Other Tools