Sergio by Serviche

Open a group text thread

start_group_text

Idempotent

Opens the one group text thread for 2 to 9 contacts who each have a phone, as the inbox's New conversation with several people checked does (an existing group for the same people is reused). Nothing is sent; texting it is send_conversational_message, which shows your person the words first. Pass the same idempotency_key when retrying.

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": {
      "clientIds": "<clientIds>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "start_group_text"
  }
}

Input Schema

Name	Required	Description	Default
`clientIds`	Yes
`idempotency_key`	Yes	Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes meaningfully beyond the annotations by clarifying that 'opens' means no message is sent and that an existing group for the same people is reused rather than duplicated. Annotations already declare idempotentHint=true, but the description explains how to use idempotency_key on retries, which is useful operational context. It does not cover permission requirements or error behavior, so not a 5.

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?

The core operation is front-loaded and each sentence carries distinct information: purpose, sibling routing, reuse semantics, retry key. The parenthetical about the inbox UI is slightly verbose but serves as a useful mental model, so it earns its place.

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?

With no output schema and only two parameters, the description covers creation semantics, non-sending behavior, reuse, and retry well. The remaining gap is the return value (presumably a thread identifier), which the agent must discover empirically.

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?

The schema documents idempotency_key fully but leaves clientIds bare (only UUID format and 2-9 item bounds), and the description compensates by establishing that these are contacts who each have a phone. That is real meaning beyond the schema's structural constraints, though it doesn't say what happens if a listed contact lacks a phone.

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: 'Opens the one group text thread for 2 to 9 contacts'. The scope constraint and analog to the inbox's 'New conversation with several people' make the operation concrete, and the explicit contrast with send_conversational_message separates it from the sibling that actually sends text.

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

Usage Guidelines5/5

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

Explicitly says nothing is sent and names the alternative tool (send_conversational_message) for the sending step, plus the note that the message is shown to the user before sending. It also states the existing-group reuse behavior and the retry convention, leaving little to inference.

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

All Sergio by Serviche 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?