Skip to main content
Glama

Openfema

by io.github.pipeworx-io

Query Dataset

query_dataset
Read-onlyIdempotent

Generic OData query against any OpenFEMA dataset. Specify the entity name (and optionally version; defaults to the verified current version) plus OData params: filter, select, orderby, top, skip. Use list_datasets to see available entities/versions and the filter syntax. Returns { metadata, records }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMax records ($top, default 50, max 1000).
skipNoRecords to skip ($skip) for paging.
entityYesDataset entity name, e.g. 'PublicAssistanceFundedProjectsDetails'.
filterNoOData $filter, e.g. "state eq 'TX' and fyDeclared eq 2023".
selectNoComma-separated $select fields, e.g. "disasterNumber,state,incidentType".
orderbyNoOData $orderby, e.g. 'declarationDate desc'.
versionNoPath version like 'v1'/'v2'/'v4'. Optional — defaults to the verified current version for known entities.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "entity": "DisasterDeclarationsSummaries",
+    "filter": "state eq 'FL' and fyDeclared eq 2023",
+    "select": "disasterNumber,state,incidentType,declarationDate"
+  },
+  {
+    "entity": "PublicAssistanceFundedProjectsDetails",
+    "orderby": "lastRefresh desc",
+    "top": 50
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. Description adds return format '{ metadata, records }' and version defaulting behavior, supplementing annotations effectively.

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, front-loaded with core function. No unnecessary details, each part earns its place.

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?

Given 7 parameters, no output schema, and reliance on OData (external standard), the description provides essential context: what, how, where to get entities, and return shape. Could mention pagination or top/default limit (default 50 is in schema but not in description) but schema covers it.

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?

Input schema covers all 7 parameters with descriptions (100% coverage). Description adds value by clarifying that version is optional and defaults to current verified version, which is not in schema. Beyond that, it mostly restates OData params.

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?

Description uses precise verb 'query' and specifies resource 'any OpenFEMA dataset'. It distinguishes from sibling 'list_datasets' by referencing it for discovery, clarifying this tool is for actual data retrieval.

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 directs users to list_datasets for available entities and filter syntax, providing clear complement. However, it does not explicitly exclude usage for datasets that may have dedicated tools (e.g., disaster_declarations), which could improve guidance.

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

All Openfema toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

The tool set has several overlapping families: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, the discovery tools (list_datasets, discover_tools, suggest_questions) all serve a 'what can I do here' purpose, and ai_visibility_check is wrapped by scan_competitor_ai_presence. The polymarket_* tools are well-differentiated, but the heavy overlap in the meta-tools makes selection error-prone.

Naming Consistency2/5

Naming is a mix of conventions with no unifying pattern: family prefixes appear as ask_pipeworx_*, pipeworx_*, and polymarket_*, while unrelated tools use bare nouns (entity_profile, recent_changes), verb-first names (validate_claim, search_within), and inconsistent styles. The three actual FEMA tools (disaster_declarations, list_datasets, query_dataset) share no prefix that ties them to the server's stated name.

Tool Count2/5

34 tools exceeds the 'too many' threshold, and the count is unjustified by the server's apparent scope: only 3 of 34 tools relate to OpenFEMA data, with the remaining 31 being a grab-bag of Pipeworx routing, Polymarket betting, memory, subscription, and AI-visibility utilities. The bulk is either redundant with the meta-routers or off-domain for a server named 'Openfema'.

Completeness2/5

For FEMA specifically, list_datasets + query_dataset covers generic read-only access and disaster_declarations adds a convenience wrapper, but the domain is extremely thin and lacks FEMA-specific conveniences (e.g., geographic aggregation, multi-dataset joins, incident summaries). For the broader Pipeworx universe the routing coverage is actually decent, but that makes the FEMA-named server's surface feel incoherent — an agent expecting a FEMA toolset finds most of its value in unrelated prediction-market and brand-visibility tools.

Resources