Skip to main content
Glama

Marden Yard Permits

watch_area

A standing watch on the same criteria that delivers each day's new permits.

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

Input Schema

NameRequiredDescriptionDefault
toNoIssued on or before, YYYY-MM-DD
zipNo5-digit site ZIP (not available for Chicago)
daysNoIssued in the last N days (default 7; anonymous max 7)
fromNoIssued on or after, YYYY-MM-DD
nameNo
limitNoMax rows (anonymous 5, keyed 50)
tradeNo
tradesNo
deliveryNo
min_valueNoMinimum permit-declared value; only permits with a reliable value match
jurisdictionNoJurisdiction slug: chicago, austin, los-angeles, seattle
community_areaNoChicago community area number
min_confidenceNoTrade confidence floor, 0-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it only discloses the daily delivery cadence. It says nothing about persistence of the watch, whether it requires an API key, how delivery is configured, or whether creating one is reversible or destructive.

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?

It is a single short sentence with no wasted words, but that brevity comes at the cost of substance; the front-loaded clause is metaphorical rather than informative.

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?

For a 13-parameter tool with no annotations and no output schema, one sentence is far too thin. An agent cannot tell what gets created, what is returned, or which of the many filter parameters matter, leaving major gaps relative to the tool's complexity.

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 moderate (69%), and the description adds no parameter meaning at all beyond the vague word 'criteria'. Thirteen parameters, including undocumented ones like name, trades, and delivery, receive no clarification, so the description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'standing watch' implies a recurring subscription that delivers new permits matching saved criteria, which distinguishes it from the one-shot siblings search_permits and permit_detail. But it never uses a concrete verb+resource like 'create a saved daily alert', so the agent must infer the operation from metaphor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over search_permits, no mention of prerequisites (API key filtering limits, jurisdiction support), and no note about managing or removing a watch once created. The only usage signal is implicit in 'each day's new permits'.

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