Skip to main content
Glama

Data Fcc

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Query

query
Read-onlyIdempotent

Run a Socrata SoQL query against a FCC Open Data dataset by resource_id (e.g. "3xyp-aqkj"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNoSoQL $group column(s).
limitNoMax rows (default Socrata 1000).
orderNoSoQL $order, e.g. "date DESC".
whereNoSoQL $where filter, e.g. "year >= 2020 AND status = 'Active'".
offsetNoPagination offset.
selectNoSoQL $select, e.g. "name, count(*) AS n".
resource_idYesDataset id, e.g. "3xyp-aqkj" (from datasets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "resource_id": "3xyp-aqkj"
-  },
-  {
-    "limit": 50,
-    "order": "facility_name ASC",
-    "resource_id": "3xyp-aqkj",
-    "select": "facility_name, license_status",
-    "where": "year >= 2020"
-  }
-]New value: +[
+  {
+    "limit": 5,
+    "resource_id": "3xyp-aqkj"
+  },
+  {
+    "limit": 5,
+    "resource_id": "3xyp-aqkj",
+    "select": "id"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "resource_id": "3xyp-aqkj"
+  },
+  {
+    "limit": 50,
+    "order": "facility_name ASC",
+    "resource_id": "3xyp-aqkj",
+    "select": "facility_name, license_status",
+    "where": "year >= 2020"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral details beyond annotations: returns JSON, uses SoQL clauses without the leading '$', and requires a resource_id. This helps the agent invoke it correctly without contradicting 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?

The description is only three sentences and each one earns its place: the first states what and where, the second explains the filtering capabilities with a key gotcha (no leading '$'), and the third states the return format. There is no filler or redundancy.

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 query tool with rich parameter schema and safety annotations, the description covers the essential invocation facts: target dataset via resource_id, supported SoQL clauses, the '$' formatting caveat, and JSON output. No critical information is missing for an agent to call it correctly.

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%, so every parameter already has a clear description and examples. The description echoes the parameter list (where/select/group/order, limit/offset) but adds no significant semantics beyond the schema, so a baseline 3 is appropriate.

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 states a specific action ('Run a Socrata SoQL query') against a specific resource ('FCC Open Data dataset by resource_id') and provides a concrete dataset ID example. This makes it clearly distinguishable from sibling tools like datasets or metadata.

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 clearly conveys how to use the tool: pass a resource_id and optionally use where/select/group/order plus limit/offset. It doesn't explicitly name alternatives or when-not-to-use cases, but the usage context is unambiguous for an agent.

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

All Data Fcc 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