Skip to main content
Glama
Sign In
roamer-x-mcp

roamer-x-mcp

by Nicolas-Prn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_space

Read-only

Retrieve a space's details and booking rules by space ID to check requirements before reserving a room.

Instructions

Details and booking rules of one space (by its space id, e.g. "LIC.4.17").

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

Input Schema

NameRequiredDescriptionDefault
space_idYes
building_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 safety is covered. The description adds that the return includes booking rules, not just static attributes, which is genuinely useful context. It says nothing about behavior on unknown ids, the effect of building_id scoping, or data richness.

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?

A single front-loaded sentence with the resource, the scope constraint, and the id format example. No filler, and the example is placed where it is immediately usable.

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?

With no output schema and zero schema description coverage, the description carries most of the burden. Naming 'details and booking rules' gives the agent a sense of the payload, but the undocumented building_id and the absence of any error/not-found behavior leave real gaps for a two-parameter lookup tool.

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 0%, so the description must compensate. It does well for space_id by giving the expected format and a concrete example ('LIC.4.17'), which the schema lacks entirely. The second parameter, building_id, is not mentioned at all, leaving its purpose (disambiguation? routing?) unexplained.

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+resource: retrieving details and booking rules for a single space, keyed by space id. The singular lookup is implicitly distinguished from list-style siblings like search_spaces and list_locations, but no sibling is named explicitly.

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?

The phrase 'one space (by its space id)' implies this is the by-id detail lookup rather than a search, so the agent can infer usage. However, there is no explicit when-to-use vs search_spaces, and no mention of prerequisites (e.g., whether the id must come from search_spaces 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