Skip to main content
Glama
Sign In
Conversational Experience Router

Conversational Experience Router

by zvyen1314-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read a public discussion room

get_public_room

Retrieve a public discussion room and its current visible messages using an actor ID and room ID, excluding content from blocked participants.

Instructions

读取一个公开讨论房间及当前可见消息。被拉黑的参与者内容不会返回。

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": {
      "actor_id": "<actor_id>",
      "room_id": "<room_id>"
    },
    "name": "get_public_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
room_idYes
actor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that content from blocked participants is not returned and that only currently visible messages are read, but it omits access/permission requirements, pagination, and whether the operation is strictly read-only.

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 compact sentences, front-loading the core read operation and then the visibility caveat. Every sentence earns its place with no waste.

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

Completeness2/5

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

No annotations and no output schema, combined with 0% parameter coverage, leave important gaps. The description conveys the read purpose and one filtering rule but does not explain actor_id or access requirements, so an agent lacks enough context to call it confidently.

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 description coverage is 0% for two required parameters (room_id, actor_id). The description implies a room must be identified but never explains room_id, and it says nothing about actor_id, so it only partially compensates for the missing schema documentation.

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 a specific verb (读取) and resource (公开讨论房间及当前可见消息), making the operation clear. It does not differentiate from sibling tools like discover_public_topics or join_public_room, so 4 rather than 5.

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?

No when-to-use or when-not-to-use guidance is given. It does not name alternatives such as join_public_room for joining or discover_public_topics for listing, leaving the agent to infer that this is simply the read-room tool.

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