Skip to main content
Glama

H1b

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.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark it read-only/idempotent, and the description adds substantial behavior: fan-out across many sources, sources_used/sources_failed semantics, 'empty section is a real no data, not a bug,' the patents soft-fail, and expected empty fda_products for small-molecule companies. This lets an agent interpret partial results correctly.

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

Conciseness3/5

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

The description is dense and front-loaded, but it is one long unstructured paragraph with redundant illustrative phrasings (seven variants of 'tell me about X') and repeats the type/interchangeability detail already in the schema. A bulleted structure would make the source/return catalog easier to consume without losing information.

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 the full burden of return values and does so thoroughly: every profile section (cik, filings, fundamentals, patents, contracts, FDA products, hiring, news, LEI) is named, plus failure/fallback semantics and input resolution behavior. Nothing essential is missing for a complex multi-source tool.

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 goes beyond it: value can be ticker, zero-padded CIK, or company name, names resolve via SEC EDGAR match, type values are interchangeable, and resolution results include resolved_from/resolved_to. It also gives concrete examples (AAPL, 0000320193, Moderna).

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 names specific verbs and resources: 'full cross-source profile of a US public company in ONE parallel call' and enumerates exactly what it returns. It also distinguishes itself from 'chaining single-pack SEC/XBRL/news lookups,' so an agent can tell it apart from more targeted tools.

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?

It explicitly instructs 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' giving an explicit when-to-use rule and the alternative it replaces. It also clarifies scope (US public companies, private companies yield resolved:false) and acceptable inputs.

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

All H1b 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

A4.1/5.0
Disambiguation3/5

Several overlapping clusters exist: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research all handle research questions, polymarket_edges and polymarket_arbitrage both scan for trading opportunities, and discover_tools/suggest_questions serve similar discovery purposes. The long, use-case-specific descriptions help, but an agent could still easily pick the wrong tool among these near-duplicates.

Naming Consistency4/5

Most tools follow a snake_case verb_noun or noun pattern (resolve_entity, validate_claim, list_subscriptions, h1b_salary), which is fairly consistent. However, there are deviations: bare verbs like recall/remember/forget/subscribe, noun-only phrases like entity_profile and recent_changes, and the ask_pipeworx_beta suffix variant break the pattern slightly.

Tool Count2/5

34 tools is well past the 25+ threshold, and the server is named 'H1b' while only 3 of the 34 tools relate to H-1B data. The rest is a sprawling mix of data research, prediction-market analytics, memory, subscriptions, AI visibility checks, and unrelated utilities like generate_llms_txt and scan_dependency — a severe scope mismatch.

Completeness4/5

As a de facto Pipeworx research platform, the surface is nearly complete: open-ended queries, grounded evidence mode, deep multi-source research, entity resolution, comparison, claim validation, subscriptions, memory, and feedback. The H-1B sub-domain covers employer, salary, and top-sponsor lookups, though the mention of green cards is a small mismatch since only LCA data is provided.

Resources