Skip to main content
Glama

SalonRenter for Muse

get_listing

Get one published listing by id. Owner contact is not included. weeklyPrice is the low end of the posted price converted to USD per week, and is null when the price is invalid. priceQuality is ok, unusual, or invalid (null when no price is posted). Treat unusual or invalid prices as unverified: do not quote them as typical, pass along priceNote, and suggest confirming with the owner. likelyJobAd marks job posts, which are not rentals.

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
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses an exclusion (owner contact is not included) and defines the semantics of weeklyPrice, its null case, and the priceQuality states. It does not cover behavior for a missing/unpublished id, permissions, or rate limits, which keeps 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?

Purpose is front-loaded in the first sentence, followed by return-value semantics and then a handling rule for unverified prices. Every sentence is dense with information an agent cannot get from structured fields, with no filler.

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?

There is no output schema, so the description must explain return values, and it covers the fields most likely to be misused (weeklyPrice, priceQuality, likelyJobAd, absent owner contact). For a one-parameter lookup this is close to complete, though the remaining result fields are undescribed.

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 0% for the single required id parameter, and the description only implies that the id identifies a listing (reinforced by 'published'). It does not state the id's format or provenance (e.g., the id returned by search_listings), so it adds only marginal meaning beyond the schema.

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 with scope: 'Get one published listing by id.' The 'one published listing' phrasing cleanly separates it from the list-returning search_listings sibling, so an agent can pick correctly without opening the 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?

Usage is clearly implied by the id-based single-record lookup and reinforced by handling instructions for the risky cases ('Treat unusual or invalid prices as unverified... suggest confirming with the owner'). It never explicitly says to obtain ids from search_listings first, so it stops short of full when/when-not routing, but the operational guidance is concrete and actionable.

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