Skip to main content
Glama

npm

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. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/destructive=false, and the description adds substantial behavioral context: it fans out across specific sources, soft-fails USPTO PatentsView after May 2025, treats empty FDA-licensed biologics as expected for small-molecule companies, and reports per-source success/failure via sources_used/sources_failed. It also specifies the private-company resolved:false behavior rather than a bare failure. No contradiction with 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 every segment earns its place given the multi-source fan-out and failure-mode details. It is front-loaded with examples and the preference directive before enumerating return sections. Slight redundancy with the schema on type/value interchangeability keeps it from 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?

With no output schema, the description carries the burden of explaining return shapes, and it does so thoroughly: it enumerates each result section (filings with pipeworx URIs, fundamentals sorted by period_end, patents, contracts, FDA products, hiring, news, LEI) plus sources_used/sources_failed. It covers resolution failure for private companies, so nothing essential is missing for an agent to call it correctly.

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?

Schema coverage is 100% (both type and value have descriptions, type has an enum). The description adds extra nuance beyond the schema: value may be a ticker, zero-padded CIK, or company name with EDGAR name resolution, and type values are interchangeable. This is useful but marginal on top of already-documented schema.

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 example queries ('Tell me about X', 'research Acme') and states the core action: produce a full cross-source profile of a US public company in one parallel call. It explicitly distinguishes itself from chaining single-pack SEC/XBRL/news lookups, so an agent can differentiate it from related research 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 contains an explicit directive: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' This states the triggering user intent and the alternative pattern to avoid, which is strong usage guidance.

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

All npm 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
Disambiguation4/5

Descriptions are exceptionally detailed and differentiate tools well; the ask_pipeworx family (stable/beta/grounded), polymarket tools, and npm lookup tools each have clear separation of intent. Minor overlap exists between polymarket_edges and polymarket_arbitrage (both surface opportunities) and between discover_tools, suggest_questions, and pipeworx_trending (all aid discovery), but descriptions mostly resolve the ambiguity.

Naming Consistency3/5

All names are snake_case and several families are consistent (get_*, list_*, search_*, ask_pipeworx, polymarket_*), but the convention is inconsistent: verb-first names (resolve_entity, validate_claim, scan_dependency) coexist with noun-first or noun-only names (entity_profile, deep_research, bet_research, recent_alerts, ai_visibility_check, pipeworx_trending, polymarket_arbitrage). No clear governing pattern beyond snake_case.

Tool Count2/5

36 tools is well over the 25-tool heavy threshold, and the majority (~29) are unrelated to the server's declared 'npm' identity — they are Pipeworx data-query, prediction-market, memory, and subscription tools. Only about 7 tools (search_packages, get_package, get_version_info, list_versions, get_downloads, scan_dependency, generate_llms_txt) actually pertain to npm. The scope is a kitchen-sink mismatch with the server name.

Completeness3/5

For npm, the read-side surface is reasonably complete: search, inspect package metadata, version listings, download counts, and a dependency-safety composite check. However, there are no lifecycle operations (publish, unpublish, deprecate, set versions/tags), leaving a notable gap, and the bulk of the server's functionality (data queries, prediction bets) belongs to an entirely different domain that can't be cohesively evaluated against the npm purpose.

Resources