Skip to main content
Glama

Palimpsest — censorship, China economy and model-eval observatory

Great Firewall: both layers

gfw_reading
Read-onlyIdempotent

Read the Great Firewall's current state at both layers in one call: live network blocking measured inside China via OONI (website, messenger and circumvention-tool reachability) joined with model-layer censorship from the Generative Firewall Index over Chinese LLMs. Takes no arguments. A combined convenience view. For one layer's full raw payload use get_signal with 'ooni-gfw' or 'generative-firewall-index'.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description only needs to add value on behavior. It does so by disclosing that two distinct datasets are joined into one response and what each covers, which is real context an agent would not get from annotations. It stops short of saying anything about data freshness, sampling window, or response shape.

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?

Three tight sentences: the deliverable first, then the scope/content of each layer, then the alternative route. Every sentence carries information an agent needs to choose and call the tool; nothing is restated from the schema beyond the necessary no-argument confirmation.

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 zero-parameter read tool with no output schema, the description covers what is measured, at which layers, and from which sources, which is enough to decide relevance and act. The only gap is that the structure of the combined response (how the two layers are presented together) is left implicit.

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 zero parameters and 100% schema coverage, the baseline is 4. The description explicitly confirms 'Takes no arguments', removing any ambiguity about whether filters or layer selection can be passed, though there is no parameter meaning to elaborate.

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 ('Read the Great Firewall's current state') and scopes it precisely to both layers, naming the two underlying sources (OONI live network blocking inside China; Generative Firewall Index model-layer censorship over Chinese LLMs). This is clearly distinguishable from get_signal, which is described as a single-layer raw payload tool.

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?

Explicitly frames the tool as a combined convenience view and names the alternative route: use get_signal with 'ooni-gfw' or 'generative-firewall-index' for one layer's full raw payload. The when-to-use and when-to-use-something-else conditions are both stated, along with the fact that it takes no arguments.

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.