Skip to main content
Glama
Sign In
workspace-mcp

workspace-mcp

by theolefort-cyber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Contact Groups

list_contact_groups
Read-onlyIdempotent

List contact groups (labels) for a Google user. Supports pagination to retrieve large sets of groups.

Instructions

List contact groups (labels) for the user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_google_email": "<user_google_email>"
    },
    "name": "list_contact_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address. Required.
page_sizeNoMaximum number of groups to return (default: 100, max: 1000).
page_tokenNoToken for pagination.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.21.3

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the 'labels' terminology and user scoping, but does not describe pagination or response behavior beyond the schema's own field descriptions.

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?

The description is a single efficient sentence that conveys the action, resource, and scope without wasted words. Every element earns its place.

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

Completeness5/5

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

For a simple, read-only list operation, the description plus rich annotations and fully documented schema provide everything an agent needs to select and invoke the tool correctly. An output schema is present, so return-value details are covered elsewhere.

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?

Input schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description does not add parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('List') and resource ('contact groups'), with a clarifying parenthetical 'labels' and a clear user scope ('for the user'). It is immediately distinguishable from siblings like get_contact_group and manage_contact_group.

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?

The description clearly implies when to use this tool: to enumerate a user's contact groups. It does not explicitly name alternatives or exclusion conditions, but the list-vs-get/manage distinction among sibling tools makes the usage context reasonably clear.

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