Skip to main content
Glama
Sign In

Oyeh

by com.amkentech.channel
OverviewDiscussionsAdmin

Invite a friend to a group

invite_to_group
Destructive

Invite one of your person's friends to a group your person owns. Only the owner invites, only friends, and only when your person asks. The friend sees the group's name, its owner, everyone in it and everyone invited, and decides. An invitation lapses after 7 days; someone who said no can be invited again only 7 days later.

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": "<group>",
      "handle": "<handle>",
      "words": "<words>"
    },
    "name": "invite_to_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesThe group's id or exact name, from my_groups
wordsYesYour person's own words asking to invite them, as they said them
handleYesThe friend's handle, e.g. @ana

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description explains what the friend sees, that the friend decides, that invitations expire after 7 days, and that someone who declined can be re-invited only after 7 days. These are meaningful behavioral details that an agent would not get from the annotations alone.

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 front-loaded with the core action and then adds exactly the constraints and lifecycle details that matter. Every sentence contributes useful information without repetition or filler.

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?

For a destructive group-invitation mutation with no output schema, the description covers eligibility, effect, visibility, expiry, and re-invitation rules. Combined with annotations and the fully documented schema, it gives an agent enough context to invoke the tool correctly.

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 description coverage is 100%, so the input schema already explains the group, handle, and words parameters in detail. The description adds contextual constraints around who can be invited but does not add parameter-level syntax or format information beyond the schema.

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 states a specific verb and resource: inviting a person's friend to a group the person owns. It distinguishes this from a generic friend invite by tying the action to an owned group, and the owner/friend constraints further disambiguate it from siblings like invite_friend.

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?

It gives clear usage conditions: only the owner can invite, only friends can be invited, and only when the person asks. It does not explicitly name alternatives such as invite_friend, so it falls short of full when/when-not/alternative guidance.

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

All Oyeh toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources