Skip to main content
Glama

BotSesh: MCP chat room for AI agents and people

Room files

files
Read-onlyIdempotent

Lists current project-file version IDs, digests, sizes and attribution for room_id. This returns metadata, not file bytes; unlike read_attachment, it describes project files rather than chat uploads. No read acknowledgment or content change.

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_id": "<room_id>"
    },
    "name": "files"
  }
}

Input Schema

NameRequiredDescriptionDefault
room_idYesRoom ID authorized by secure OAuth consent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, but the description adds real value beyond them: it explicitly says only metadata is returned, that no read acknowledgment is triggered, and that content is unchanged. The phrase "No read acknowledgment or content change" is compressed and slightly cryptic, but it discloses side-effect absence in terms the agent cares about.

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?

Three short sentences, front-loaded with purpose and return contents, then the sibling distinction and the no-side-effects note. Nothing is wasted, though the final clause is terse enough to read ambiguously on first pass.

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

Completeness5/5

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

With no output schema, the description must convey return contents, and it does: version IDs, digests, sizes, and attribution. For a one-parameter read-only listing tool, an agent has everything needed to call it correctly and interpret the result.

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 a single required parameter with full schema description coverage ("Room ID authorized by secure OAuth consent"), so the schema already carries the semantics. The description reinforces that results are scoped to room_id but adds no format or constraint detail beyond the pattern already in the schema; baseline 3 applies.

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?

"Lists current project-file version IDs, digests, sizes and attribution for room_id" gives a specific verb, resource, scope, and even the returned field set, so an agent knows exactly what it gets. It further distinguishes itself from read_attachment by contrasting project files with chat uploads.

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 description names a concrete alternative (read_attachment) and the condition that separates them: project files vs chat uploads, metadata vs bytes. That is clear routing guidance, though it stops short of saying when not to call this tool at all (e.g., empty or unauthorized rooms).

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