Skip to main content
Glama

Hex Pm

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

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

The description goes far beyond the readOnly/openWorld/idempotent annotations by disclosing fan-out behavior across specific sources, soft-fail handling for USPTO patents, what an empty section means, and the resolved:false response for private companies. This gives the agent accurate expectations about partial or empty results and non-fatal source failures.

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 every section earns its place: examples at the top convey intent quickly, the fan-out list pre-explains expected results, and edge cases are folded into the parameter explanation. It could be slightly tighter, but it is front-loaded and logically organized.

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 carries full responsibility for return semantics, and it does so thoroughly: it names every output section, explains URIs, covers source failure, distinguishes expected no-data from bugs, and documents all accepted input shapes. An agent has enough context to invoke the tool and interpret results correctly.

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?

Although schema coverage is 100%, the description enriches both parameters substantially: it explains that type accepts 'company' or 'ticker' interchangeably, that value can be a ticker/CIK/name, that names resolve via SEC EDGAR, and how unknown or private companies are handled. This is meaningful guidance beyond the bare schema text.

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 verb+resource precisely: build a full cross-source profile of a US public company in one parallel call. It clearly differentiates from simpler single-pack SEC/XBRL/news lookups and sibling tools like resolve_entity or deep_research by emphasizing holistic multi-source aggregation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent when to prefer this tool: "ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view." It also specifies accepted input forms (ticker, CIK, company name) and the private-company edge case, leaving no ambiguity about when it applies.

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

All Hex Pm 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.8/5.0
Disambiguation2/5

Several tools occupy overlapping question-answering territory: ask_pipeworx_beta currently behaves identically to ask_pipeworx, while ask_pipeworx_grounded, deep_research, and validate_claim all route the same data catalog and differ mainly in output guarantees. The six Polymarket tools also split edge detection, arbitrage, and fill-risk in ways that are easy for an agent to conflate. Clear exceptions like the memory and subscription trios keep it from a 1.

Naming Consistency4/5

Names are uniformly lowercase snake_case and most follow a readable verb-first or domain-prefixed pattern (get_package, list_releases, scan_dependency, ask_pipeworx_*). The Polymarket family uses noun phrases after a prefix (polymarket_edges, polymarket_fill_risk) and a few names are noun-first (entity_profile, recent_changes), which is a minor inconsistency rather than chaos.

Tool Count2/5

35 tools is well beyond the comfortable 3-15 range and even above the 16-25 heavy range. The broad Pipeworx data scope justifies some expansion, but identical ask_pipeworx_beta, six overlapping Polymarket tools, and unrelated utility families (Hex.pm, AI visibility, memory, llms.txt) suggest bloat rather than deliberate scoping.

Completeness4/5

Within its main data-access purpose, the surface is unusually complete: query (ask_pipeworx), grounded verification (ask_pipeworx_grounded/validate_claim), deep research, entity resolution/profiling, comparison, change feeds, and search-within are all present, and memory/subscription subdomains have full CRUD. There are minor gaps for the package side (no docs/dependents) and the hodgepodge of domains makes a single 'complete' surface hard to define, but no workflow hits a hard dead end.

Resources