China Footnotes

Get current notices

get_current_notices

Read-onlyIdempotent

List dated notices in effect on a date (today in Asia/Shanghai unless date is given) for places in China Footnotes, such as holiday traffic controls, temporary closures and special opening hours, each with its sources. Filter by city or place. Only notices the editors have entered are included; this is not a live news feed, and an empty list does not mean nothing has changed.

Input Schema

Name	Required	Description
`city`	No	Lowercase city id, as listed in cities when search_places is called with no arguments. Omit for all cities.
`date`	No	Date in Asia/Shanghai, YYYY-MM-DD; default today. Stored notices only; not a live feed.
`placeId`	No	Only notices for this place id (from search_places).

Output Schema

Name	Required	Description
`date`	Yes
`notices`	Yes
`sources`	No	Source id index. Dates are stored evidence dates, not rendering dates; null means unavailable.
`timezone`	No
`dataVersion`	No
`renderedFor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 31, 2026

changedInput schema / properties / city / description

Previous value: -"City id. Covered: shanghai, beijing, xian, chengdu, chongqing, hangzhou."New value: +"Lowercase city id, as listed in cities when search_places is called with no arguments. Omit for all cities."

changedInput schema / properties / date / description

Previous value: -"Date in Asia/Shanghai, YYYY-MM-DD. Stored rules only; not live availability."New value: +"Date in Asia/Shanghai, YYYY-MM-DD; default today. Stored notices only; not a live feed."

changedInput schema / properties / placeId / description

Previous value: -"Only notices for this place id."New value: +"Only notices for this place id (from search_places)."

Changed11 schema fields changedOct 16, 2026

addedInput schema / properties / city / maxLength
```
Added value: +200
```

addedInput schema / properties / date

Added value: +{
+  "description": "Date in Asia/Shanghai, YYYY-MM-DD. Stored rules only; not live availability.",
+  "maxLength": 10,
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / placeId / maxLength
```
Added value: +100
```

addedOutput schema / properties / dataVersion

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / notices / items / properties / sources / items / properties / accessedAt
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / notices / items / properties / sources / items / properties / checkedAt
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / notices / items / properties / sources / items / properties / id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / notices / items / properties / sources / items / properties / verificationMethod
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / renderedFor
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / sources

Added value: +{
+  "additionalProperties": {
+    "properties": {
+      "accessedAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "checkedAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "kind": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "label": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "publishedAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "url": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "verificationMethod": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "description": "Source id index. Dates are stored evidence dates, not rendering dates; null means unavailable.",
+  "type": "object"
+}

addedOutput schema / properties / timezone

Added value: +{
+  "const": "Asia/Shanghai"
+}

Changed1 schema field changedOct 13, 2026
- changedOutput schema / properties / notices / items / properties / sources / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
First observedOct 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description adds substantive context: results are editor-curated rather than live, each notice carries its sources, and an empty list is not evidence of no change. These are exactly the interpretation caveats an agent needs.

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 action and scope, then the filtering and the caveats. Slightly dense in the first sentence but every clause (scope, examples, sources) earns its place; the empty-list caveat is well placed at the end.

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?

For a read-only, fully documented, output-schema-backed list tool, the description covers action, scope, defaults, filtering, and the key interpretive limitation. Nothing an agent needs to call it correctly or to interpret an empty result 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?

All three parameters are fully documented in the schema (100% coverage), including the lowercase city id convention, the YYYY-MM-DD Asia/Shanghai date default, and place id provenance from search_places. The description only restates the city/place filtering and timezone default, adding little beyond the schema, so the baseline 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?

States a specific verb and resource ('List dated notices in effect on a date') with the geographic scope (places in China Footnotes) and concrete examples (holiday traffic controls, temporary closures, special opening hours). This is clearly distinct from the place-lookup siblings like get_place and search_places.

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 explicit defaults ('today in Asia/Shanghai unless date is given') and filter guidance ('Filter by city or place', or omit for all). It also sets expectations about when the result is authoritative: 'Only notices the editors have entered are included; this is not a live news feed, and an empty list does not mean nothing has changed.' No sibling alternative is named, which keeps it from a 5.

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

All China Footnotes 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.

Resources

Need Help?