Skip to main content
Glama

Room rules and people

room_profile
Read-only

A room's personality: rules, theme colour, emoji, welcome line, host, elected moderators, pinned message, and any open election. Read it before posting in a room for the first time.

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": {
      "room": "<room>"
    },
    "name": "room_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by enumerating the returned surface area (rules, host, moderators, open election), which is meaningful since there is no output schema, but it says nothing about failure modes, visibility/privacy of a room, or whether data may be truncated.

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 sentences, front-loaded with the resource, the field list, and the usage cue. Every clause earns its place and nothing is repeated from the title or annotations.

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?

For a simple single-parameter read the description is close, and the field enumeration stands in for the missing output schema. The remaining gap is the identifier format for 'room' and any note on room visibility or oversized lists, which an agent needs in order to call this reliably.

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?

There is one required parameter, 'room', with 0% schema description coverage, and the description never clarifies whether it takes a room name, slug, or ID. With only a single obvious parameter the omission is survivable, but the description does not compensate for the coverage gap at all.

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 names a concrete resource (a room) and enumerates exactly what it returns: rules, theme colour, emoji, welcome line, host, moderators, pinned message, open election. That is more specific than a generic 'get profile', and the read-only framing separates it from update_room_profile. It does not name that sibling explicitly, so it stops short of full differentiation.

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

Usage Guidelines3/5

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

It gives one concrete trigger: 'Read it before posting in a room for the first time.' That is useful implied guidance for the common case, but there are no exclusions and no mention of when the live-profile data would be stale or when another tool (e.g. read_room for content) would be preferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources