Skip to main content
Glama

District Listings

Check District Availability

get_availability
Read-onlyIdempotent

Returns the published availability of one District workspace: whether it is available now, available from a date, needs confirming or unavailable, how many desks it holds, and its published price. Optional inputs: desks (the team size), to learn whether it holds them, and startMonth (YYYY-MM), to learn whether it is free in time. This is the operator's published availability, the same as the District listing page shows. needs_confirming means the operator has not confirmed the space is free for that time, so it is not a statement that the space is available. requestViewingUrl is the District listing page, where viewings are requested. Read only: it cannot book, enquire or show contact details.

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

Input Schema

NameRequiredDescriptionDefault
desksNoTeam size, to check the listing holds them
listing_idYesThe workspace id (from search_listings)
startMonthNoMonth the team wants to move in, as YYYY-MM

Output Schema

NameRequiredDescriptionDefault
desksYes
priceYes
sourceYes
listingYes
verifiedAtYes
availabilityYes
requestViewingUrlYesThe District listing page, where viewings are requested

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description instead invests in semantics the annotations cannot carry: it clarifies that results mirror the operator's public listing page, and warns that needs_confirming 'is not a statement that the space is available' — a genuinely non-obvious interpretive caveat. It also gives meaning to requestViewingUrl as the viewing-request destination.

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?

Front-loaded with what is returned, then the optional inputs, then status semantics, then the read-only constraint — a logical ordering. The needs_confirming explanation is slightly convoluted and the enumeration of statuses plus fields in sentence one is dense, but no sentence is filler.

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?

An output schema exists, so return shape need not be restated; the description instead supplies the interpretive layer (status meanings, published-vs-guaranteed distinction, viewing URL purpose) that an agent needs to act correctly. Nothing material is missing for a 3-parameter read-only lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description still adds intent-level meaning by explaining that desks means team size ('to check the listing holds them') and startMonth tests time-based freedom rather than being a plain date filter. The required listing_id is only explained via the schema ('from search_listings'), which keeps it from a 5.

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?

States a specific verb and resource ('Returns the published availability of one District workspace') and enumerates the exact result states — available now, available from a date, needs_confirming, unavailable — plus desks count and price. An agent can tell this apart from get_listing or search_listings without opening any schema.

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?

Explains what the optional inputs are for ('desks ... to learn whether it holds them', 'startMonth ... to learn whether it is free in time') and closes with an explicit exclusion: 'Read only: it cannot book, enquire or show contact details.' That steers an agent away from using it for booking/enquiry, though it never names the sibling tool that would handle those actions.

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