Skip to main content
Glama
HMEI83

ModuHaus-MCP

by HMEI83
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DB_PASSWORDYesYour PostgreSQL password

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_granny_flat_rulesA

Get granny flat / secondary dwelling approval rules for an Australian state.

Returns the state-level rule plus any council-level rules on record. In
Queensland the state sets no standard at all, so the council rules are the
only real figures - the state row exists to say so.

Args:
    state: State or territory code, e.g. NSW, VIC, QLD, WA, SA, TAS, ACT, NT.
    lga: Optional council name filter, e.g. "Moreton Bay". Partial matches work.
compare_statesA

Compare granny flat rules across all eight states and territories.

Use this for questions like "which state is easiest to build in" or "where can I build the largest granny flat". Comparable figures only - a state whose value is unknown is listed separately rather than omitted, so it is never silently dropped from a ranking.

check_data_freshnessA

List rules that have not been re-verified recently.

Planning law changes often - Victoria alone saw five amendments touching
secondary dwellings between 2023 and 2025. Call this before relying on a
rule for a decision, and warn the user about anything flagged stale.

Args:
    max_age_months: Rules older than this many months are reported as stale.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool serves a distinct purpose: checking data freshness, fetching rules for a specific state, and comparing across states. There is no overlap or ambiguity in what they do.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (check_data_freshness, get_granny_flat_rules, compare_states). The naming style is uniform and predictable.

Tool Count5/5

With 3 tools, the set is well-scoped for a niche domain like Australian granny flat regulations. Each tool is necessary and focused, fitting within the ideal 3-15 range.

Completeness5/5

The domain is fully covered: fetching specific rules, comparing all states, and ensuring data freshness. There are no obvious gaps for a read-only regulatory lookup service.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources