Skip to main content
Glama

room

The Enoch and Melchizedek rooms: every passage on the shelf that names Enoch or Melchizedek, with links.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact name recorded in rooms.json; an unknown name returns the available names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Exact name recorded in rooms.json; an unknown name returns the available names."
    • removedInput schema / properties / name / enum
      Removed value: -[
      -  "enoch",
      -  "melchizedek"
      -]
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it omits that this is a read-only operation, whether results are scoped to a user or edition, how large the result can get, and how the 'links' are shaped. It does implicitly convey the returned content, but the unknown-name fallback lives only in the schema, not the description.

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?

A single, front-loaded sentence with no filler; the return content is stated up front. Its brevity is not the problem — the missing context is.

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 one-parameter lookup tool with no output schema and no annotations, the description does say what comes back, which is the essential piece. It falls short on the concept of a 'room' and on scope/behavior, leaving an agent to guess how this differs from sibling retrieval tools.

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 description coverage is 100% and the single 'name' parameter is fully documented in the schema, including the unknown-name fallback. The description adds only two concrete example values ('Enoch', 'Melchizedek'), which is marginal value beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete return payload ('every passage on the shelf that names Enoch or Melchizedek, with links'), which is more specific than a restatement of the name 'room'. However, it presents the tool as if it only covers two fixed rooms, while the schema takes an arbitrary 'name' recorded in rooms.json; an agent cannot tell whether this is a room-browser, a fixed topical query, or something extensible to other 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?

There is no when-to-use guidance and no mention of alternatives such as search_shelf, which plausibly overlaps with this topical retrieval. The agent must infer from the description alone that this is a curated browse-by-room operation rather than a free-text search.

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