Skip to main content
Glama
Sign In
gws-admin-mcp

gws-admin-mcp

by antct11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

groupsettings_get

Retrieve a group's access settings, including join/post/view permissions, archiving, and moderation options.

Instructions

Get a group's access settings (who can join/post/view, archiving, moderation, etc.).

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": {
      "groupEmail": "<groupEmail>"
    },
    "name": "groupsettings_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupEmailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

The verb 'Get' indicates a read-only operation, which is transparent. However, with no annotations, the description carries full burden for disclosing behavior. It does not mention whether special permissions are required, how the response is structured, or any other side effects. The description is adequate but not rich.

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, focused sentence that efficiently conveys the tool's purpose with concrete examples. There is no redundant information or filler.

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

Completeness3/5

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

For a simple read tool with no output schema, the description lists some settings but leaves 'etc.' open-ended. It does not describe the return format or any pagination/error behavior. It is minimally complete but lacks details that would help an agent know what to expect in the response.

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%, and the description does not reference the 'groupEmail' parameter at all. While the parameter name is self-explanatory, the description fails to add any explicit meaning beyond the schema's type and property name, which is insufficient given the low coverage.

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 clearly states the function: 'Get a group's access settings'. It specifies the resource (group access settings) and provides examples ('who can join/post/view, archiving, moderation, etc.'), distinguishing it from sibling tools like groups_get which would retrieve general group information.

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?

The description implies when to use the tool (when you need a group's access settings) but provides no explicit guidance on alternatives or exclusions. It does not mention groups_get or other sibling tools, so the context is inferred rather than stated.

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