Skip to main content
Glama

Group and measure building permits

analyze_permits
Read-onlyIdempotent

Counts and mix of matching building permits, grouped by up to three of: city, county, state, workType, workGroup, status, stage, constructionType, propertyType, valueBand, trade, sector, jobKind, appliedMonth, issuedMonth, or activityMonth. Metrics: count, sumJobValue, medianJobValue, avgJobValue, valueKnown, sumUnits, and contractors (how many distinct contractors). Value metrics come with valueKnown, the share of permits that state a value. filters take the search_permits names. Groups under five permits are omitted. Returns no permit records, names, or contacts. Does not use credits.

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

Input Schema

NameRequiredDescriptionDefault
limitNoGroups to return, at most 1,000. This is not a record count.
filtersNoThe search_permits filter names, as an object.
groupByNoUp to 3 dimensions, e.g. ["city","issuedMonth"].
metricsNoDefaults to ["count"]. "contractors" counts distinct contractors.
orderByNoA metric or dimension name to sort groups by.
directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses a small-group suppression rule (groups under five omitted) and that it consumes no credits, both behaviorally important. It also clarifies valueKnown meaning. It does not explain pagination or ordering defaults, which keeps it short of a 5.

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?

Content is front-loaded with the core action and immediately follows with dimensions and metrics. The long enumeration of groupable fields makes it dense, but every element carries informational value and no sentence is wasted.

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 nested-filter aggregation tool with no output schema, the description covers dimensions, metrics, suppression, and credit behavior adequately. The absence of an output schema means the exact result shape (group keys plus metric fields) is only implied, leaving a minor gap.

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?

With 83% schema coverage the baseline is 3, but the description adds real meaning: it explains valueKnown as the share of permits stating a value, notes the up-to-three grouping limit, and clarifies that filters use search_permits names. This exceeds what the schema alone conveys.

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 names a concrete verb pair (counts and mix), the exact resource (building permits), and the enumerable dimensions it can group by. An agent can immediately distinguish this aggregation tool from search_permits or get_permit.

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?

It states the tool returns no permit records, names, or contacts, and that filters reuse search_permits names, which implicitly routes record-level lookups to search_permits. It does not explicitly contrast with the sibling count_permits, so the when-not guidance is partial rather than complete.

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