Skip to main content
Glama
loomiomcp
by soil-dev

get_group

Read-onlyIdempotent

Retrieve a group's full record by numeric ID, short key, or URL handle in one call, including public groups the user has not joined, plus membership and parent details.

Instructions

One group by numeric id, short key or URL handle: 1 call; works for public groups the user has not joined. Returns the full record (members_can_* flags included, billing subscription dropped) plus member, membership, parent, url. 403 = hidden; unknown = 404 (open-DCR deployments say 'not visible' for both).

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": {
      "id_or_key_or_handle": "<id_or_key_or_handle>"
    },
    "name": "get_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_key_or_handleYesGroup numeric id, short key or URL handle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.17
    • changedInput schema / properties / id_or_key_or_handle / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^[A-Za-z0-9_-]+$",
      -    "type": "string"
      -  },
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +    "type": "string"
      +  },
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  }
      +]
  2. Addedv0.0.13

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description goes well beyond them: it discloses public-group visibility, that billing `subscription` is dropped from the record, retained `members_can_*` flags, and the 403-hidden vs 404-unknown mapping including the open-DCR 'not visible' variant. That is exactly the kind of error and payload-shaping context annotations cannot express.

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?

Front-loaded with the identifier forms and single-call nature, then return shape, then error semantics — no filler sentences. The trailing open-DCR parenthetical is niche detail that slightly crowds an otherwise tight definition.

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?

With no output schema, the description compensates by naming the returned fields (`member`, `membership`, `parent`, `url`) and what is excluded, plus status-code semantics. For a one-parameter read tool, nothing an agent needs to call or interpret it is missing.

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 coverage is 100% and the single parameter's own description already says 'Group numeric id, short key or URL handle,' so the description largely restates it. No extra format or syntax guidance is added, so baseline 3 applies.

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?

States a specific verb and resource ('One group') with the accepted identifier forms, and the '1 call'/'One group' framing immediately separates it from the sibling list_groups. An agent knows exactly what this returns versus a listing tool.

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?

'works for public groups the user has not joined' is a concrete usage condition that tells the agent this does not require membership or elevated auth. It stops short of naming alternatives (list_groups, search_content) or stating when not to use it, so it is a clear context statement rather than a full routing rule.

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