Skip to main content
Glama
Sign In

Oyeh

by com.amkentech.channel
OverviewDiscussionsAdmin

Set a group's end date

set_group_end_date
Idempotent

Set, move or clear the end date of a group your person owns (the group ends at the start of that day, UTC). Only the owner, only when your person asks. Invitations show it.

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>"
    },
    "name": "set_group_end_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNotrue to take the end date off
groupYesThe group's id or exact name, from my_groups
ends_onNoThe new end date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The description adds useful behavior beyond the annotations: the group ends at the start of that day in UTC, owner permissions apply, and invitations show the end date. Since annotations already declare the safety profile, these added details make the mutation behavior reasonably transparent.

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 short, front-loaded, and every clause earns its place by covering the action, date semantics, authorization, and invitation effect. There is no unnecessary repetition.

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 three-parameter mutation with full schema coverage and annotations, the description is largely complete: it explains the effect, ownership requirement, UTC day boundary, and invitation visibility. It could say more about error conditions or return behavior, but no output schema is present and the core guidance is sufficient.

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 schema already documents group, ends_on, and clear. The description adds context for date semantics and clearing, but it does not meaningfully expand parameter meaning beyond the schema baseline.

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 clearly states a specific verb and resource: set, move, or clear a group's end date. It distinguishes the operation from immediate group ending by focusing on scheduling an end date, but it does not explicitly name or contrast with siblings such as end_group.

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: the person must own the group, and this should only be done when the person asks. It does not explicitly mention alternatives like end_group or leave_group, so the routing guidance is present but not exhaustive.

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