Ruforge

Назначить встречу

ruforge_meeting_create

Назначить встречу форум-группы: разовую (scheduled_at) или регулярную серию (repeat: день недели + неделя месяца + время; RuForge создаст встречи вперёд, участники получат уведомления и .ics). Только владелец/модератор. Спросите у пользователя дату/правило и ссылку на видеозвонок; длительность по умолчанию 180 мин (формат «3 часа»), для короткого формата — 90.

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": {
      "access_token": "<access_token>",
      "group_id": "<group_id>",
      "title": "<title>"
    },
    "name": "ruforge_meeting_create"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Например «Форум-группа: встреча №1»
`repeat`	No	Регулярная серия вместо scheduled_at
`group_id`	Yes
`video_link`	No
`access_token`	Yes	access_token из ruforge_profile_check / ruforge_profile_confirm (действует 7 дней). Не показывайте его пользователю
`duration_min`	No
`scheduled_at`	No	Разовая встреча: дата-время ISO 8601 с таймзоной, например 2026-11-05T19:00:00+03:00

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026

addedInput schema / properties / access_token

Added value: +{
+  "description": "access_token из ruforge_profile_check / ruforge_profile_confirm (действует 7 дней). Не показывайте его пользователю",
+  "type": "string"
+}

removedInput schema / properties / user_id

Removed value: -{
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "user_id",
-  "group_id",
-  "title"
-]New value: +[
+  "access_token",
+  "group_id",
+  "title"
+]

AddedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only declare the mutation safety profile (readOnly=false, destructive=false, idempotent=false); the description adds real side-effect detail beyond that — meetings are generated ahead of time, participants get notifications and an .ics file, and the call is permission-gated to owner/moderator. It omits that idempotentHint=false means repeated calls can create duplicate meetings, which is the one behavior an agent would want warned about.

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?

Dense but front-loaded: the mode distinction comes first, then constraints and defaults. Two long sentences carry a lot of information with almost no filler; the duration-default clause at the end is the only part that could be tightened.

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 7-parameter mutation tool with a nested repeat object and no output schema, the description covers modes, mutual exclusivity, permissions, side effects (notifications, .ics), defaults, and what to collect from the user. Nothing essential to invoking it correctly 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?

Schema coverage is only 57%, but the description compensates well: it explains the repeat semantics (weekday + week of month + time), states that repeat is used *instead of* scheduled_at, tells the agent to obtain video_link from the user, and gives default duration guidance (180 min, short format 90, natural-language '3 часа'). Only title and group_id get no added meaning, which is fine for a trivial string field.

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?

States a specific verb and resource (создать встречу форум-группы) and immediately splits it into the two concrete modes the schema supports: one-off via scheduled_at and recurring series via repeat. An agent can tell exactly what operation is performed and what the two shapes of it are without opening the schema.

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?

Gives clear context: only owner/moderator may call it, and it instructs the agent to ask the user for the date/rule and the video link before calling. It does not discuss any alternative (e.g. a sibling that edits or cancels a meeting), but no such sibling exists in the provided list, so the guidance is sufficient for selection.

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

All Ruforge tools Inspect

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

Need Help?