Skip to main content
Glama

Walkable spaces in AREMES HQ and the RSMAD museum

list_spaces
Read-only

Every walkable 3D space by the artist Ryan Seslow: the floors and rooms of AREMES HQ in Brooklyn, the eleven galleries of RSMAD (the Ryan Seslow Museum of Art & Design), the Sculpture Park and the street outside. Each opens in any web browser, on a phone or in a VR headset. Returns name, link, description, floor and access (most are free).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_spaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional words to filter by name or description, e.g. "museum", "vaults", "third floor".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavioral context about compatibility (any browser, phone or VR headset), the returned fields (name, link, description, floor, access) and that most spaces are free. It stops short of saying whether the list is exhaustive, ordered, or paginated, but the gaps are minor for a read-only catalog.

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?

Two sentences, front-loaded with the scope of the catalog, with no filler. The long enumeration of locations earns its place by telling the agent what the data contains, though it could be trimmed slightly.

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

Completeness4/5

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

For a one-parameter, read-only listing with no output schema, the description covers the contents, the return fields and the browsing medium. Missing only ordering/pagination and differentiation from list_spaces_for_license.

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 100% and the single optional query parameter is fully documented in the schema with examples. The description never mentions the filter at all, so it adds nothing beyond the schema; baseline 3 applies.

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?

Names a specific resource ('Every walkable 3D space by the artist Ryan Seslow') and enumerates its scope: AREMES HQ floors, the eleven RSMAD galleries, the Sculpture Park and the street. An agent knows exactly what comes back, though it does not distinguish this from the sibling list_spaces_for_license, which sounds like a near-identical listing.

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 or when-not-to-use guidance and no mention of alternatives, despite list_spaces_for_license sitting among the siblings. The only usage-adjacent text is the parenthetical that most spaces are free, which is context rather than routing guidance.

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