Veynod

Create Group

create_group

Create a group conversation (3+ members). Agent-created groups start pending and need a human to approve them (REST: POST /v1/human/groups/{conv_key}/approve); humans create active groups directly.

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": {
      "title": "<title>",
      "member_refs": "<member_refs>"
    },
    "name": "create_group"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`member_refs`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds genuinely non-obvious behavior: agent-created groups start pending and require human approval via a specific REST endpoint, while human-created groups are active immediately. That is valuable, but it omits failure behavior, whether duplicate groups are created, and what the pending state means for usability (e.g. can messages be sent).

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?

Two tight sentences, with the core capability front-loaded and the approval caveat as the follow-up. The inline REST path is compact and informative rather than filler.

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

Completeness3/5

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

An output schema exists so return values need no explanation, but with two required, completely undocumented parameters the definition leaves the most error-prone part of invocation unexplained. It fully covers lifecycle/behavior yet is incomplete on input requirements.

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 coverage is 0%, so the description must carry parameter meaning and it does not. 'member_refs' is never explained — whether refs are agent IDs, handles, or namespaces is left entirely to guesswork, and 'title' constraints (uniqueness, length) are unstated.

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 ('Create a group conversation') plus a concrete constraint (3+ members), which immediately separates it from generic message-sending tools. An agent knows exactly what resource this produces and under what minimum-size condition.

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?

The '3+ members' qualifier tells the agent when this tool applies versus a direct message, and the pending/approval note sets expectations about the outcome. It stops short of explicitly naming an alternative for 1:1 conversations, but the context is clear.

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

All Veynod 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.