Skip to main content
Glama

Stat Lv

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

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses important runtime behavior: USPTO PatentsView API sunset soft-fail, empty sections are expected and not bugs, sources_used/sources_failed semantics, and private-company resolution behavior. This gives an agent realistic expectations about partial data and 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 densely informative and front-loaded with trigger phrases and the main directive before enumerating sources and return fields. It earns its length given the tool's many cross-source behaviors, though it could be tightened with light structural formatting for even easier scanning.

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 explaining what is returned, and it does so thoroughly: CIK/name resolution, recent filings, fundamentals, patents, contracts, FDA products, H-1B hiring, news, LEI, and sources_used/sources_failed. It also covers failure modes and expected empty results, which is exactly what an agent needs to correctly interpret the response.

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?

The schema already covers both parameters well at 100% coverage, so the baseline is 3. The description adds useful context by enumerating the three acceptable value shapes (ticker, zero-padded CIK, company name), explicitly stating that 'type' accepts both values interchangeably, and noting what name resolution does via SEC EDGAR.

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's first sentence names exact user phrasings ('Tell me about X', 'research Acme', 'brief me on Tesla') and defines the resource: a full cross-source profile of a US public company in one parallel call. This makes the tool's purpose concrete and distinguishable from single-source lookup and comparison siblings.

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?

Usage guidance is explicit and action-oriented: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also defines acceptable inputs and the expected result for private companies, so an agent knows exactly when to invoke this tool and when it is the right alternative to chained lookups.

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

All Stat Lv 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
Disambiguation3/5

Several tools form overlapping families (ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research, plus the six polymarket_* tools), and ask_pipeworx_beta is currently an exact behavioral duplicate. The long descriptions usually disambiguate them, but an agent could still struggle to quickly choose between similar research and edge-detection tools.

Naming Consistency3/5

Names are uniformly snake_case and prefix families like pipeworx_* and polymarket_* help, but there is no consistent verb_noun pattern: subjects, table_meta, recent_alerts, and entity_profile are noun phrases while remember, generate_llms_txt, and compare_entities are action-first. The mixed conventions are readable but less predictable than a uniform pattern.

Tool Count2/5

34 tools is well into the 'too many' range for a single tool set, even if each is individually documented. Several could plausibly be consolidated, such as ask_pipeworx_beta, the polymarket edge tools, and the AI-visibility pair.

Completeness4/5

For its broad stated purpose, the set covers the full lifecycle: lookup/research, entity profiles, comparisons, claim validation, prediction-market edge analysis, memory, subscriptions, and discovery. Minor gaps exist, such as no direct fetch-by-URI tool or subscription update path, but most workflows have a clear route.

Resources