kolmo-mcp-server

Permit source freshness

get_permit_data_freshness

Read-onlyIdempotent

Source-freshness telemetry for the permit catalog. Returns per-jurisdiction last-verified dates, a per-jurisdiction source-health rollup (which cities have a reachable / gone / blocked official source right now), and the latest results from the weekly source-of-truth snapshot pipeline (HTTP status, change-detection vs prior fetch). Failures are classified: missing means the page is gone, blocked means the host refused our fetch and is NOT evidence the source is gone. Use to answer "how current is this fee/timeline?" or to surface confidence in a permit answer. The /permits/data-quality page exposes the same signals.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max snapshots to return (default 5, newest first)
`jurisdictionSlug`	No	Optional jurisdiction filter (e.g., "seattle", "bellevue"). When omitted, returns rollup across all jurisdictions.

Output Schema

Name	Required	Description	Default
`totals`	No
`coverage`	No
`pipeline`	Yes
`publicView`	Yes
`attribution`	Yes
`sourceHealth`	No
`jurisdictions`	No
`changeDetection`	No
`recentSnapshots`	No
`howToReadFailures`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

changedOutput schema / properties / attribution / properties / citeAs / description

Previous value: -"Ready-made citation line. Use verbatim."New value: +"Citation line; use verbatim."

changedOutput schema / properties / attribution / properties / primarySource / description

Previous value: -"Present when Kolmo verified but does not author the fact — cite both."New value: +"Kolmo verified, did not author: cite both."

changedOutput schema / properties / attribution / properties / sourceUrl / description

Previous value: -"The specific page these facts render on. Link this, not the site root."New value: +"The page to link, not the site root."

Changed4 schema fields changedOct 10, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / attribution / additionalProperties
```
Removed value: -true
```

Changed7 schema fields changedSep 3, 2026

changedInput schema / properties / limit / description

Previous value: -"Max snapshots to return (default 50, newest first)"New value: +"Max snapshots to return (default 5, newest first)"

removedOutput schema / properties / attribution / properties / contractorLicense
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / attribution / properties / note
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / attribution / properties / organization
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / attribution / properties / retrievedFrom
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / attribution / properties / url
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / attribution / required

Previous value: -[
-  "organization",
-  "contractorLicense",
-  "url",
-  "sourceUrl",
-  "citeAs",
-  "retrievedFrom",
-  "note"
-]New value: +[
+  "sourceUrl",
+  "citeAs"
+]

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "attribution": {
+      "additionalProperties": true,
+      "properties": {
+        "citeAs": {
+          "description": "Ready-made citation line. Use verbatim.",
+          "type": "string"
+        },
+        "contractorLicense": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "organization": {
+          "type": "string"
+        },
+        "primarySource": {
+          "description": "Present when Kolmo verified but does not author the fact — cite both.",
+          "type": "string"
+        },
+        "retrievedFrom": {
+          "type": "string"
+        },
+        "sourceUrl": {
+          "description": "The specific page these facts render on. Link this, not the site root.",
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "organization",
+        "contractorLicense",
+        "url",
+        "sourceUrl",
+        "citeAs",
+        "retrievedFrom",
+        "note"
+      ],
+      "type": "object"
+    },
+    "changeDetection": {},
+    "coverage": {},
+    "howToReadFailures": {},
+    "jurisdictions": {},
+    "pipeline": {
+      "type": "string"
+    },
+    "publicView": {
+      "type": "string"
+    },
+    "recentSnapshots": {},
+    "sourceHealth": {},
+    "totals": {}
+  },
+  "required": [
+    "pipeline",
+    "publicView",
+    "attribution"
+  ],
+  "type": "object"
+}

AddedApr 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description adds genuinely non-obvious semantics by defining `missing` vs `blocked` and warning that `blocked` is NOT evidence the source is gone. It also discloses that data comes from a weekly snapshot pipeline, which sets expectations about staleness. It stops short of stating latency or whether checks run live on request.

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?

Front-loads purpose, then payload contents, then failure semantics, then use cases — a sensible information order with no filler. The enumerated payload list is dense but each clause carries distinct information; only the trailing data-quality page pointer is arguably optional.

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

Completeness5/5

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

An output schema exists, yet the description still summarizes the shape of the three returned sections, which is enough for an agent to know what it will get and how to interpret failure classifications. With zero required parameters and full schema coverage, nothing needed for correct invocation is missing.

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 description coverage is 100% and both parameters document themselves, including the default of 5 and the all-jurisdictions behavior when omitted. The description only echoes 'per-jurisdiction' scoping and adds no new syntax or edge-case guidance, so baseline 3 applies.

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?

States a specific verb+resource ('source-freshness telemetry for the permit catalog') and enumerates the three payloads: per-jurisdiction last-verified dates, source-health rollup, and snapshot-pipeline results. That makes it unmistakable against content siblings like get_permit_timeline or list_permit_jurisdictions, which return permit substance rather than provenance metadata.

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?

Gives concrete triggers: 'Use to answer "how current is this fee/timeline?" or to surface confidence in a permit answer,' and points to the equivalent /permits/data-quality page. It does not state when NOT to call it (e.g., that it is not a substitute for the actual fee/timeline lookup), which keeps it short of a 5.

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

All kolmo-mcp-server tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.