Skip to main content
Glama

Data Cincinnati

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.7/5.0
Behavior5/5

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

Despite annotations declaring readOnly/openWorld/idempotent/non-destructive, the description adds substantial behavioral context: it fans out across many sources, returns sources_used/sources_failed, treats empty sections as real 'no data,' soft-fails on the USPTO sunset, and explains that a lack of FDA products is expected for small-molecule-only companies. These details go far beyond the annotations.

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 long, but it earns its length given there is no output schema and the tool spans many sources. It is front-loaded with the core purpose and usage preference, then systematically covers return sections and input semantics. It could be slightly better organized with bullets or shorter sentences, hence not a 5.

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 complex multi-source tool with no output schema, the description is remarkably complete. It documents all major return sections, input types, expected empty results, soft-failure behavior, and private-company handling. An agent has enough context to invoke the tool correctly and interpret unusual results without external guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description significantly enriches both parameters: it clarifies that 'company' and 'ticker' are interchangeable, explains that 'value' can be a ticker, zero-padded CIK, or name, and describes resolution behavior including resolved_from/resolved_to and the private-company failure mode. This greatly exceeds the schema's basic descriptions.

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 opens with concrete user phrasings and states the core action: 'full cross-source profile of a US public company in ONE parallel call.' It clearly names the resource (SEC EDGAR, XBRL, patents, contracts, FDA, H-1B, news, GLEIF) and distinguishes itself from chained single-pack lookups, making its purpose unambiguous.

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 explicitly says 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' which gives a clear when-to-use signal. It also explains accepted inputs and the private-company edge case. It does not name every sibling alternative or explicitly state when not to use it, so it stops short of a 5.

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

All Data Cincinnati 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.9/5.0
Disambiguation2/5

Several tool clusters have unclear boundaries: ask_pipeworx, ask_pipeworx_beta (explicitly identical), ask_pipeworx_grounded, and deep_research all route the same queries, and the five polymarket_* tools overlap in opportunity scanning. entity_profile, compare_entities, and recent_changes also pull similar company data, making tool selection genuinely ambiguous.

Naming Consistency4/5

All tool names are snake_case with a mostly verb-first convention (ask_pipeworx, scan_dependency, validate_claim, resolve_entity). A few noun-first names like polymarket_edges, entity_profile, and recent_alerts deviate slightly, but the pattern is predictable and readable throughout the 34-tool set.

Tool Count2/5

At 34 tools, the surface is heavy for what the server name (Data Cincinnati) implies, and only 3 tools actually relate to Cincinnati open data. The rest spans prediction markets, npm analysis, AI visibility, memory, and subscriptions, suggesting either scope creep or a misleading server name.

Completeness3/5

The research workflow is fairly covered: discovery (discover_tools, suggest_questions), query (ask_pipeworx), grounding (ask_pipeworx_grounded), verification (validate_claim), profiling (entity_profile), comparison (compare_entities), and monitoring (subscribe, recent_changes). However, notable gaps exist — no direct single-source raw query, no export/visualization, no subscription or alert management details beyond basic CRUD, and the Cincinnati-specific surface is thin (no geospatial or full-catalog access).

Resources