Skip to main content
Glama

Ooni

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ooni Measurements

ooni_measurements
Read-onlyIdempotent

List recent raw OONI measurements for a domain and/or country — individual probe results with timestamp, network (ASN), anomaly/confirmed flags, and a link to the full measurement on OONI Explorer. Use after ooni_site_reachability to inspect specific blocking evidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (1-50, default 10).
domainNoWebsite domain, e.g. "twitter.com".
countryNo2-letter country code filter, e.g. "IR".
confirmed_onlyNoOnly measurements with confirmed blocking fingerprints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "IR",
+    "domain": "twitter.com",
+    "limit": 20
+  },
+  {
+    "confirmed_only": true,
+    "country": "CN",
+    "domain": "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 already declare readOnlyHint=true and destructiveHint=false. The description adds value by enumerating output fields (timestamp, ASN, anomaly/confirmed flags, link) and the link to OONI Explorer, giving behavioral context beyond annotations.

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, no filler. First sentence defines purpose and output; second provides usage guidance. Front-loaded and efficient.

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?

Covers purpose, usage, and key output fields. With no output schema and 4 optional parameters, the description gives enough context for basic invocation. Minor gap: no mention of default limit or ordering, but not critical.

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 description coverage is 100%, with clear descriptions for all 4 parameters. Description mentions domain and country but does not add meaning beyond the schema. Baseline 3 is appropriate as schema does the heavy lifting.

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 uses specific verb 'list' and resource 'raw OONI measurements', clearly states scope by domain/country, and distinguishes from sibling OONI tools by advising use after ooni_site_reachability for inspecting blocking evidence.

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?

Explicitly states when to use ('Use after ooni_site_reachability to inspect specific blocking evidence'), providing clear context. Does not mention exclusions but effectively positions the tool within a workflow among siblings.

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