ph-civic-data-mcp

by xmpuspus

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Server health and data-source catalog

get_data_freshness

Read-onlyIdempotent

Check data source freshness and cache status to determine if re-fetching is needed.

Instructions

Server health and data-source catalog probe.

Doubles as the version and health endpoint: returns server_version so an agent can confirm which release it is talking to. Also returns the full upstream-source catalog: cache TTLs, freshness expectations, and licenses. Use it to judge whether a stale cached response is fine or a re-fetch is needed.

Examples: get_data_freshness() # the only call, it takes no arguments

On failure: this tool calls no upstream itself, so it always returns a dict. source_health is a process-local, in-memory registry, not a database. It starts empty on a cold process and fills as fetch_with_retry runs calls, so a fresh restart always reports an empty dict here.

Returns: server_version, server_name, transport, tool_count, asof, sources (list of {source, source_url, freshness, cache_ttl_seconds, license}), source_health (per-host {last_success_at, last_failure_at, last_error, last_latency_ms, success_count, failure_count}), cache_age (per-cache {size, ttl_seconds}), note.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0May 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description reveals important behavioral details: it makes no upstream calls, always returns a dict, and that source_health starts empty on a cold process. This transparency helps the agent understand runtime behavior.

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?

The description is well-structured with sections for purpose, example, failure behavior, and return fields. It is informative without being overly verbose, and the example clarifies that no arguments are needed.

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?

The description fully covers what the tool returns, including edge cases (empty cache on cold start, note field), and explains when to use it. Given the zero-parameter complexity, it provides all necessary context for correct invocation and interpretation.

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?

The tool has zero parameters and the schema coverage is 100% (empty schema). The description adds no parameter-specific meaning because none exist. Per the rubric, with high schema coverage and no parameters, the baseline score of 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?

The description clearly states the tool's dual function as a server health/version probe and a data-source catalog, and explicitly explains its purpose: to judge whether a stale cached response is acceptable or a re-fetch is needed. This distinguishes it from sibling data-fetching tools.

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

Usage Guidelines5/5

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

The description provides direct usage guidance: 'Use it to judge whether a stale cached response is fine or a re-fetch is needed.' It also notes the tool doubles as a version/health endpoint, giving clear context for when to invoke it over other tools.

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

Deploy Server