Skip to main content
Glama

get_group

Read-onlyIdempotent

Get a student group's details by its obfuscated ID: returns name, auto-add email-domain rules, category, and timestamps. Use this to inspect group settings without retrieving member lists.

Instructions

Fetch one student group by its obfuscated id.

    Returns the group's name, its auto-add email-domain rules, its category and its
    timestamps. It does NOT return the member list - v2 has no endpoint that reads
    memberships back, only `add_group_memberships` and `remove_group_memberships`
    that change them.

    The last-changed timestamp is `updated_at`, not `modified_at`.

    Requires the `student-groups:read` OAuth scope.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
created_atNo
updated_atNo
category_idNo
rule_email_domainsNo
send_course_enrollment_emailNo
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds substantial behavioral context beyond those annotations: it does not return the member list, v2 has no membership-read endpoint, the relevant timestamp is `updated_at` rather than `modified_at`, and the `student-groups:read` OAuth scope is required. This meaningfully shapes agent expectations.

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?

Every sentence earns its place: the fetch action, returned fields, the membership limitation, the timestamp clarification, and the authorization requirement. The most important information is front-loaded, and nothing is redundant or padded.

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?

Given a single simple parameter, an output schema, and strong annotations, the description is fully sufficient. It covers what is returned, what is not returned, a subtle timestamp naming pitfall, and the required OAuth scope. No critical operational detail is missing.

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 schema only declares `id` as a required string with no description, giving schema description coverage of 0%. The description compensates by specifying that the id is the group's obfuscated id, which is essential for correct invocation. It could add a bit more detail about the expected format or provenance, but for a single parameter this is solid 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 opens with a specific verb and resource: 'Fetch one student group by its obfuscated id.' It clearly identifies the action, the target, and the selection key, and it differentiates from list-style sibling tools. It also enumerates what the response contains, leaving no ambiguity about the tool's function.

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 provides clear context for when to use this tool: fetching one group by id, not listing groups or retrieving memberships. It explicitly names sibling tools `add_group_memberships` and `remove_group_memberships` when explaining what this tool does NOT do. However, it does not explicitly say to use `list_groups` when multiple groups are needed, so exclusions are slightly incomplete.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server