Skip to main content
Glama

SalonRenter for Muse

city_rents

Weekly salon suite and chair rent by city, ordered by spaces within 25 miles descending. Only markets with at least 8 usable posted prices. Do not quote unusual or invalid listing prices as typical. Counts are spaces within 25 miles.

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": "city_rents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/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 disclose real behavior: a 25-mile radius, a minimum sample threshold of 8 usable posted prices, and a data-quality caveat. It omits what a caller most needs behaviorally — default and maximum page size, whether offset pagination applies, and whether an empty market set is returned or dropped.

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 is front-loaded and the sentences are short, but 'spaces within 25 miles' is stated twice, and the data-quality caution is mixed in with scope rules rather than separated. It is readable but has avoidable redundancy for a four-sentence description.

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

Completeness3/5

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

Semantics of the returned numbers are explained (weekly rent, 25-mile space counts, 8-price minimum), which is the hardest part. But with no output schema, no annotations, and three entirely undocumented parameters, an agent still cannot determine pagination defaults or how the state filter interacts with the city grouping.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters (state, limit, offset), so the description must compensate and does not: neither 'state' nor the paging parameters are mentioned anywhere. The only partial signal is 'by city', which hints at market grouping but never explains that a state filter narrows results.

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 first clause states the specific resource (weekly salon suite and chair rent) and its aggregation unit (by city), plus the ordering rule. That is enough to separate it from listing-level siblings such as get_listing and search_listings, though the description never states an explicit action verb like 'return' or 'report'.

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: the tool is for market-level rent benchmarking, and the caution 'Do not quote unusual or invalid listing prices as typical' guides downstream presentation. However, there is no explicit when-to-call guidance, no exclusion conditions, and no pointer to a sibling for listing-level or per-space data.

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