Skip to main content
Glama

LodgeDeck

by io.github.maxbeech

get_str_rules

Return the short-term rental rules for one jurisdiction: whether a licence is required, primary-residence rule, annual night cap, zoning restriction, listing-number display rule, registration URL and enforcement notes. Every field is an object { value, source, confidence }; an unconfirmed field is value:null with confidence:"unverified", never guessed. Free, no API key needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesJurisdiction slug (e.g. austin-tx) or a "City, ST" string.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It transparently details the return format: every field is an object with value, source, confidence; unconfirmed fields are null with 'unverified', never guessed. This goes beyond basic purpose.

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?

Two sentences, no waste. Purpose is front-loaded, and every sentence adds value.

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 simple tool with one parameter and no output schema, the description is quite complete. It explains return format, fields, and confidence handling. Minor gap: no mention of error conditions or rate limits, but free tool likely has none.

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% with a clear description of the 'city' parameter. The tool description adds no further meaning beyond the schema, which is adequate. Baseline 3.

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?

The description clearly states the tool returns short-term rental rules for a jurisdiction, listing specific fields. It is a specific verb+resource and distinguishes from siblings by focusing on rules vs eligibility or tax.

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 description indicates it returns rules for one jurisdiction, implying the need to specify a jurisdiction. It adds 'Free, no API key needed' as usage guidance. However, it does not explicitly state when to use or not use vs alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LodgeDeck toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool serves a distinct purpose: eligibility check, tax lookup, rules retrieval, and jurisdiction listing. Descriptions clearly differentiate them with no overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (check_str_eligibility, get_lodging_tax, get_str_rules, list_jurisdictions), making them predictable and easy to understand.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose of providing short-term rental regulation and tax information. Each tool earns its place without unnecessary bloat or deficiency.

Completeness4/5

The tool set covers the core workflows: checking eligibility, retrieving taxes, obtaining rules, and listing jurisdictions. Minor additions like jurisdiction-level details or booking fee info could be added, but the surface is largely complete for the stated purpose.

Resources