Skip to main content
Glama

Openfema

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

Schema Changelog

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

  1. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
    • changedInput schema / properties / value / description
      Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, and the description adds substantial context: source fan-out, USPTO soft-fail, GDELT→GNews fallback, expected-empty fda_products, resolved:false for private companies, and the meaning of sources_used/sources_failed. This is far beyond what annotations alone provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with examples and the core purpose, then organized from inputs to outputs. It is long, but most sentences carry real operational value; minor redundancies include the repeated type-interchangeable note and the aside about person/place coming soon.

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?

With no output schema, the description fully carries the return-value burden: it enumerates cik, filings with URIs, fundamentals, patents, contracts, fda_products, hiring, news, LEI, and failure semantics. Nothing essential for invoking or interpreting the result appears missing.

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%, and the schema already documents both parameters, including interchangeable type values and allowed value shapes. The description mostly restates these points with examples and adds only minor detail like 'names now resolve via SEC EDGAR company-name match.'

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as a 'full cross-source profile of a US public company in ONE parallel call' and backs it with concrete user phrasings. However, it does not explicitly differentiate itself from research-oriented siblings like deep_research or compare_entities, instead contrasting only with generic 'single-pack SEC/XBRL/news lookups.'

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?

It gives explicit guidance: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also explains accepted input forms and private-company behavior. It does not address sibling alternatives or state when this tool should not be used.

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