Skip to main content
Glama

List project groups

list_project_groups
Read-only

The company's groups of projects — one per client, department or site: each with its projects and its people (everybody on its projects, and 'explicit' those the administrator put in by hand), and the projects in no group. In a project of a group, only the group's people are offered and found when picking a person; in a project in no group, only the people in no group; somebody on a project is always offered in it. The company's administrator only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint true, destructiveHint false, openWorldHint false), and the description adds real value on top: an authorization requirement (company administrator only) and the membership-resolution semantics — only the group's people are offered in a grouped project, only ungrouped people in an ungrouped project, and project members are always offered. That is substantive behavioral context an agent would not otherwise have. It stops short of describing the response shape or ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two long sentences with stacked parentheticals ('(everybody on its projects, and 'explicit' those the administrator put in by hand)') and a trailing clause 'and the projects in no group' grafted onto a noun phrase. The access constraint, arguably the most actionable fact, is buried at the end. Front-loading the action and flattening the nesting would help, though the density does pack genuine information.

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 no parameters, no output schema and moderate complexity, the description is close to complete: it explains what the entities are, how membership behaves, and who may call it. The remaining gap is what the returned objects actually contain (group fields, project counts, people lists), which an agent calling blind would still have to discover.

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

Parameters4/5

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

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description does not waste space restating an empty schema.

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 identifies the resource precisely: the company's groups of projects, one per client/department/site, each carrying its projects and people, plus ungrouped projects. The verb 'list' is carried only by the tool name — the prose never says it returns a collection — and no sibling is named, but the resource is specific enough that an agent can distinguish it from set_project_group or move_project_to_group.

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 implied by the data model: this is the read path for inspecting groups and who belongs to them, which the mutation siblings (set_project_group, set_project_group_person, move_project_to_group) presuppose. The only explicit guidance is the access prerequisite, 'The company's administrator only.' There is no stated when-to-use versus alternatives and no exclusion conditions.

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