Skip to main content
Glama
Sign In
JoinCloud

JoinCloud

by kushneryk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

roomInfo

Read-onlyIdempotent

Retrieve detailed information about a JoinCloud workspace room, including participants, settings, and room name, to facilitate collaboration and task management.

Instructions

Get room details including name, participants, and settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "roomInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomIdNoRoom name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by specifying exactly what data fields are returned (name, participants, settings), compensating for the lack of an output schema.

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?

Single, efficient sentence of seven words. Front-loaded with action verb 'Get' and every word contributes meaningful information about the operation or return value.

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 simple read-only lookup tool with one parameter and good safety annotations, the description is reasonably complete. It compensates for missing output schema by detailing the returned fields, though explicitly stating this operates on a specific room identifier would strengthen it.

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 coverage is 100% with the roomId parameter fully described as 'Room name' in the schema. The description does not mention parameters, but with complete schema coverage, this meets the baseline expectation.

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?

States specific verb 'Get' and resource 'room details', and lists returned fields (name, participants, settings). However, it doesn't explicitly clarify this retrieves a single specific room versus the sibling 'listRooms' which presumably returns multiple rooms.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus alternatives like 'listRooms' or 'messageHistory', nor does it mention prerequisites (e.g., needing a roomId from listRooms first).

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

Deploy Server

Other Tools