Skip to main content
Glama

Virtual spaces and apartments for license

list_spaces_for_license
Read-only

Virtual spaces and apartments for license in three WebXR buildings on Union Street, Brooklyn (AREMES HQ, AREMES Commercial, AREMES Residential). A licensee fills a space with their own images, videos and 3D models. These are licenses for virtual spaces, not physical premises or housing. Returns each unit with its building, floor, kind, size, page, prices for one month, six months and one year (paid in full), and whether it is open.

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_for_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional: "Space for License", "Studio", "One Bedroom", "Two Bedroom" or "Penthouse".
buildingNoOptional: one building.
open_onlyNoOnly units that are open. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 and the description's job is to add context — which it does by enumerating the returned fields, including that prices are for one month, six months and one year paid in full, and that each unit carries an open flag. The clarification that these are virtual-space licenses rather than real estate prevents a serious misreading. It omits pagination behavior and result-size expectations, keeping it below a 5.

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?

Three sentences, each doing distinct work: identifying the inventory, defining what a license means, and listing the returned fields. The key disambiguation ('not physical premises or housing') is placed before the return-value detail, so the reader is corrected early. No filler or repetition of schema content.

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?

With no output schema, the description correctly compensates by enumerating the returned fields, and all three optional filters are documented in the schema. What is missing is any sense of scale or paging — 'page' is mentioned only as a returned field, with no statement about how many units come back or how to traverse them. For a read-only listing tool this is a minor gap, not a blocking one.

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 every parameter (kind, building, open_only) carries its own description and, for building, an enum, so the schema does the heavy lifting. The description adds conceptual meaning (what a 'kind' represents in the licensing context) but no filtering syntax or interaction detail beyond the schema. Baseline 3 is appropriate.

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?

The description names a specific resource (virtual spaces/apartments for license in three named WebXR buildings) and states exactly what a call returns: each unit with building, floor, kind, size, page and three price tiers plus open status. That is far more than a restatement of the name. It stops short of a 5 because it never distinguishes itself from the sibling list_spaces, so an agent must infer the difference from names alone.

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?

Usage is implied rather than stated: an agent can infer this is the browse step before start_space_license, and the sentence 'A licensee fills a space with their own images, videos and 3D models' hints at the licensing workflow. There is no explicit when-to-use, no exclusion, and no routing to list_spaces or the start_* tools. The 'not physical premises or housing' clarification disambiguates the concept, not the tool choice.

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