Skip to main content
Glama

Oracle — Skyline Certified Records

by io.github.Skyline-Roofing
OverviewDiscussionsAdmin

list_changes_since

Poll for what changed since a date instead of re-pulling everything: newly certified records, superseded (old->new) pairs, and reconfirmed records. Example: {"since":"2026-10-01","collection":"ok_property_permits"} returns permits certified after that date (new weekly Oklahoma City reroofing permits). Sources are re-checked weekly (Sundays, 00:00 UTC). Omitting collection scopes to ok_roofing_insurance only. Free, no API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNook_property_permits only: "Norman" or "Oklahoma City" (alias jurisdiction_city accepted).
sinceYesISO 8601 date or datetime, e.g. "2026-10-01"
stateNoTwo-letter state code, e.g. "OK".
topicNoExact topic / permit type, same values as search_records.
countyNook_property_permits only: "Cleveland" or "Oklahoma" (alias jurisdiction_county accepted).
subjectNoExact category, same values as search_records.
collectionNoWhich collection to poll; default ok_roofing_insurance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
+  "description": "ok_property_permits only: \"Norman\" or \"Oklahoma City\" (alias jurisdiction_city accepted).",
+  "type": "string"
+}
    • changedInput schema / properties / collection / description
      Previous value: -"See search_records — same default/roster."New value: +"Which collection to poll; default ok_roofing_insurance."
    • addedInput schema / properties / collection / enum
      Added value: +[
+  "ok_roofing_insurance",
+  "ok_property_permits"
+]
    • addedInput schema / properties / county
      Added value: +{
+  "description": "ok_property_permits only: \"Cleveland\" or \"Oklahoma\" (alias jurisdiction_county accepted).",
+  "type": "string"
+}
    • changedInput schema / properties / since / description
      Previous value: -"ISO 8601 date or datetime"New value: +"ISO 8601 date or datetime, e.g. \"2026-10-01\""
    • addedInput schema / properties / state / description
      Added value: +"Two-letter state code, e.g. \"OK\"."
    • addedInput schema / properties / subject / description
      Added value: +"Exact category, same values as search_records."
    • addedInput schema / properties / topic / description
      Added value: +"Exact topic / permit type, same values as search_records."
  2. Changed1 schema field changed
    • addedInput schema / properties / collection
      Added value: +{
+  "description": "See search_records — same default/roster.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the refresh cadence (weekly, Sundays 00:00 UTC), the default scoping when `collection` is omitted, and that access is free with no API key. It does not describe pagination or ordering of results, and does not need a destructive/safety note for a poll operation.

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-loaded with the core purpose and value proposition before the example and operational notes. It is dense but each sentence does work; the parenthetical 'new weekly Oklahoma City reroofing permits' is slightly verbose but grounds the example usefully.

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 no output schema and no annotations, the description covers the essentials: return categories, freshness cadence, default scope, and auth/cost model. It is complete enough to call correctly, with only result ordering/pagination left unspecified.

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%, so the baseline is 3, but the description adds value beyond the schema: it clarifies the default value for `collection` (ok_roofing_insurance when omitted) and provides a concrete example payload with its expected output. The `since` semantics are illustrated concretely rather than merely restated.

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 and resource ('poll for what changed since a date') and enumerates the three return categories: newly certified records, superseded old->new pairs, and reconfirmed records. It explicitly frames itself against re-pulling everything, so an agent can tell it apart from search_records without opening either schema.

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 opening clause 'instead of re-pulling everything' clearly signals the incremental-sync use case versus a full re-pull via search_records. It gives an example invocation and default-scope behavior, but does not state explicit when-not conditions or name the sibling alternative directly.

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

All Oracle — Skyline Certified Records toolsInspect
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.

Resources