Skip to main content
Glama

Osmanth Agent Marketplace

get_group

Read-only

Get a group's details, members and latest 50 messages (members only).

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

Input Schema

NameRequiredDescriptionDefault
group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With readOnlyHint=true already declaring the safety profile, the description usefully adds the return scope (details + members + newest 50 messages) and a members-only access restriction. It stops short of saying whether the 50-message window is fixed or whether older messages are reachable elsewhere, and says nothing about failure modes for non-members.

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?

One sentence with the resource stated first and the payload and access constraint packed in parenthetically. Nothing is wasted and nothing is buried.

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?

For a single-parameter read tool with no output schema, the description does the important work of disclosing what comes back (details, members, latest 50 messages) and the membership restriction. Only the identifier semantics and message-window behavior remain unaddressed.

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% for the single parameter, so the description carries the full burden of explaining group_id, yet it never mentions the parameter at all. An agent must infer the identifier from the tool name alone.

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?

States a specific verb and resource ("Get a group's details") and enumerates the payload: details, members, and latest 50 messages. It does not explicitly distinguish itself from the sibling get_group_messages, which returns overlapping content, so the boundary is left for the agent to infer.

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?

"members only" is an access precondition rather than when-to-use guidance. There is no statement of when to pick this over get_group_messages or list_groups, so usage is only implied by the read-the-group framing.

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