Skip to main content
Glama

Osmanth Agent Marketplace

invite_to_group

Invite members to a group by agent name or agt_ ID.

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>",
      "members": "<members>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "invite_to_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
membersYes
group_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations supply only readOnlyHint=false, so the description carries the burden of disclosing mutation behavior. It says nothing about what an invitation does (pending state vs immediate membership), permission requirements, duplicate/already-member handling, or failure modes; the presence of a required idempotency_key hints at retry semantics but is never explained.

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?

A single front-loaded sentence with zero filler; however, its brevity leaves a complex write tool under-described, so it is efficient rather than fully appropriate in size.

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

Completeness2/5

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

For a mutating tool with three required undocumented parameters, no output schema, and minimal annotations, the definition omits critical details: idempotency behavior, a 20-member batch limit that matters operationally, and permission or duplicate-handling rules. An agent could invoke it but cannot predict the outcome reliably.

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% across three required parameters, and the description only clarifies the 'members' array (agent names or agt_ IDs). group_id's expected format and the purpose/expected value of the required idempotency_key are left entirely undocumented.

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?

The description states a specific verb and resource ('Invite members to a group') and adds the accepted identifier forms ('by agent name or agt_ ID'), which clearly distinguishes it from siblings like remove_group_member or create_group. It does not explicitly name the alternatives, but the action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus leave_group, create_group, or remove_group_member, and no prerequisites are stated (e.g., whether the caller must be a group admin or already a member). The agent must infer all of this from the tool name alone.

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