Skip to main content
Glama

Ooni

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ooni Site Reachability

ooni_site_reachability
Read-onlyIdempotent

Check whether a website is blocked or censored in a specific country, using OONI network measurements from volunteer probes. Returns counts of OK, anomalous, confirmed-blocked, and failed measurements over the window plus a blocking assessment — e.g. is bbc.com blocked in China, is twitter.com blocked in Iran. Great-Firewall / national-censorship / internet-freedom research.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window in days (default 30, max 365).
domainYesWebsite domain, e.g. "www.bbc.com" or "twitter.com". A full URL is accepted (the host is extracted).
countryYes2-letter country code, e.g. "CN", "IR", "RU".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "IR",
+    "domain": "twitter.com"
+  },
+  {
+    "country": "CN",
+    "days": 90,
+    "domain": "www.bbc.com"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive, which the description complements by detailing return values (counts of OK, anomalous, confirmed-blocked, failed). No contradictions.

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?

Two sentences: one defines purpose and return, second gives examples and use cases. Every sentence adds value, no fluff. Front-loaded with the core action.

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 read-only tool with 3 parameters fully described in schema and return values explained, the description is complete enough. No output schema is needed since the description covers the response shape.

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 coverage is 100%, so baseline is 3. The description does not add significant meaning beyond the schema—it restates example values but no extra explanation of parameter behavior or constraints.

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 starts with a clear verb-resource pair 'Check whether a website is blocked or censored' and uses examples like 'bbc.com blocked in China' to illustrate. It distinguishes from sibling OONI tools by specifying site reachability versus app blocking or trends.

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 description provides usage context ('Great-Firewall / national-censorship / internet-freedom research') and concrete examples. It does not explicitly list when not to use or name alternatives, but the context is clear enough for agents to infer appropriate use cases.

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

All Ooni 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