Skip to main content
Glama
Sign In
Dilix MCP

Dilix MCP

Official
by Dilix-Ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

analyze_zoning

Retrieve zoning classification, HCD compliance status, and state-law overrides for any US address.

Instructions

Returns zoning classification, HCD compliance status, and state-law overrides (SB-9, SB-79, AB-2011, AB-130, Builder's Remedy) for any US address.

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": {
      "address": "<address>"
    },
    "name": "analyze_zoning"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name
stateNoTwo-letter state code (e.g. CA)
addressYesFull street address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description must carry behavioral burden. It only states what is returned, but does not disclose if the operation is read-only, authentication needs, rate limits, or side effects.

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?

Single sentence that is concise and front-loaded with key return items. No extraneous words.

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

Completeness2/5

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

Given the complexity of zoning analysis, the description lacks explanation of what HCD compliance means, conditions for state-law overrides, or how to interpret results. No output schema, making it insufficient for an informed agent.

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 coverage is 100% with each parameter described. Description adds overall context but no extra parameter-level detail beyond schema. Baseline score of 3 is appropriate.

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?

Description clearly states the tool returns zoning classification, HCD compliance status, and specific state-law overrides for any US address. This distinguishes from sibling tools like analyze_deal or find_opportunities.

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?

Implied usage for zoning analysis, but no explicit guidance on when to use vs alternatives like lookup_property or get_entitlement_roadmap. No exclusions or prerequisites mentioned.

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

Deploy Server

Other Tools