Skip to main content
Glama
Baneado98

muni-dev-cost

estimate_by_units

Estimate municipal fees for multifamily projects using Living Unit Equivalents (LUE). Avoids overestimation by applying a fractional LUE per unit, returning per-unit and total line items.

Instructions

Estimate the total MUNICIPAL FEES for a MULTIFAMILY / mixed-use project by LUE (Living Unit Equivalent) — units × LUE-per-unit — the way cities actually bill multifamily. Captures that a small apartment unit is a FRACTION of a single-family LUE (≈0.6), so it doesn't overstate MF fees the way a flat per-unit estimate does. Returns per-unit and extended line items; override the LUE factor with the jurisdiction's adopted one. Explicit about exclusions (land, construction, financing). Pass 'jurisdiction' or 'address', 'units', optionally 'dev_type' (default multifamily), 'lue_per_unit' and 'meter_size'. PREMIUM: pay per call with x402 (USDC on Base) or set a prepaid key (MUNI_DEV_COST_KEY).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jurisdictionNo'City, ST' or city name. Provide this OR address.
addressNoUS street address. Provide this OR jurisdiction.
unitsYesNumber of units in the project (REQUIRED).
dev_typeNoDevelopment type (default multifamily).
lue_per_unitNoLUE per unit override (default by dev_type, e.g. multifamily ≈ 0.6).
meter_sizeNoWater meter size per unit (default 5/8").
Behavior4/5

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

With no annotations, the description provides significant behavioral context: it explains the LUE method, exclusions, return of line items, override capability, and premium pricing. Lacks error handling or state mutation details.

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

Conciseness4/5

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

The description is a single information-dense paragraph, front-loaded with the core purpose. Every sentence adds value, covering method, exclusions, parameters, and pricing. Could be slightly better structured for readability.

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?

Given 6 parameters and no output schema, the description is quite complete: it explains the key concept (LUE), parameter overrides, exclusions, and pricing. Could be improved by noting the output format or sample results.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds valuable context on LUE (fraction of single-family), default values, and the relationship between parameters. It enhances understanding beyond the schema's basic descriptions.

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 estimates municipal fees for multifamily projects using LUE, contrasting with flat per-unit estimates. It specifies the resource (fees by LUE) and distinguishes from siblings like 'estimate_dev_cost'.

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 explains when to use it (multifamily/mixed-use projects) and how it differs from flat estimates. It lists parameters but does not explicitly state when not to use it or refer to sibling tools for other cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Baneado98/muni-dev-cost'

If you have feedback or need assistance with the MCP directory API, please join our Discord server