Skip to main content
Glama

District Listings

Open a District Listing

get_listing
Read-onlyIdempotent

Returns one published District workspace by id (from search_listings): its name, type, operator's public name, area, postcode and postcode district, desk range, published price (on the basis the operator quotes it, stating whether VAT is included), its price for each commitment length the operator has set, its availability, the day the operator last confirmed it, and url, its District listing page, where viewings are requested and enquiries are made. Read only: it returns no contact details and cannot book or enquire.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe workspace id (from search_listings)

Output Schema

NameRequiredDescriptionDefault
listingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description goes further by stating it returns no contact details and cannot book or enquire, which is genuine behavioral context an agent needs before deciding whether it can satisfy a user request. It does not mention failure behaviour for unpublished or missing ids.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and scope are front-loaded in the first clause, which is good. But the single sentence then unrolls a long list of return fields ('name, type, operator's public name, area, postcode...') that an output schema already declares, and the 'and url, its District listing page' construction is grammatically tangled.

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 single-id read tool with an output schema, annotations, and full parameter coverage, nearly everything an agent needs is present, including the read-only, non-transactional limit. The only real gap is guidance on what happens for unpublished or invalid ids.

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?

There is only one parameter, and the schema already documents it as 'The workspace id (from search_listings)' at 100% coverage. The description repeats the same provenance hint rather than adding format, validation, or lookup guidance, so the schema does the work and baseline 3 applies.

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?

Opens with a specific verb and resource: 'Returns one published District workspace by id', and immediately ties the id to its source tool, search_listings. That distinguishes it cleanly from search_listings and get_availability without needing the sibling schemas.

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?

The parenthetical '(from search_listings)' tells the agent where the required id originates, implying the search-then-open workflow. It does not state when not to use it, nor does it compare against get_availability, so the routing is clear but not exhaustive.

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