Skip to main content
Glama

Crypto Feeds

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/openWorld/idempotent annotations, the description discloses soft-fail behavior for USPTO PatentsView, explains that an empty fda_products section is expected for small-molecule-only companies, clarifies that empty results are real 'no data' rather than bugs, and documents sources_used/sources_failed. This is far more than annotations alone provide.

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 packs many distinct behavioral facts and return-field details that no structured data carries. It is front-loaded with purpose and usage, and each clause adds information; slight redundancy with the schema's `type` explanation prevents 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 must explain return values, and it does: it enumerates cik, company_name, resolved_from/to, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, and LEI, plus sources_used/sources_failed. It also covers edge cases like private companies, empty sections, and soft failures, making it complete for a tool of this complexity.

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 input schema already covers both parameters with 100% description coverage, so the baseline is 3. The tool description adds value with concrete examples ('AAPL', '0000320193', 'Moderna'), explains that `type` values are interchangeable, and clarifies that names resolve via SEC EDGAR's company-name match. This lifts it above baseline.

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 leads with concrete user phrasings ('Tell me about X', 'research Acme') and then states a specific deliverable: 'full cross-source profile of a US public company in ONE parallel call'. It clearly differentiates from single-pack SEC/XBRL/news lookups, so an agent understands exactly what resource the tool addresses.

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 says 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' giving a direct when-to-use rule. It also specifies accepted input shapes and what happens for private companies (resolved:false with notes), so the agent knows when and how the tool applies.

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

All Crypto Feeds 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 are nearly indistinguishable in role: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are all variants of the same router, with the beta version explicitly noted as currently identical to the stable one. The six Polymarket tools also overlap heavily around edge-finding, arbitrage, and fill-risk analysis, making misselection likely.

Naming Consistency3/5

Names are uniformly snake_case and groupable into prefixes like polymarket_* and pipeworx_*, but the set does not follow a consistent verb_noun convention. Noun-first names like entity_profile and recent_alerts sit alongside verb-first names like read_feed and validate_claim, and product-name suffixes such as ask_pipeworx_beta/grounded add further inconsistency.

Tool Count2/5

At 34 tools, the surface is well past the 25+ threshold and far broader than the 'Crypto Feeds' name suggests. The set spans feed reading, general data research, prediction markets, AI-brand visibility audits, npm dependency scanning, memory, and subscriptions, making it feel like a platform-wide dump rather than a focused MCP server.

Completeness3/5

The broad research workflow is well covered with query, grounded answer, deep research, entity profiles, comparisons, fact-checking, and entity resolution. However, feed functionality is read-only with no feed management, subscription types do not include crypto feeds despite the server name, and there is no dedicated tool for resolving the advertised pipeworx:// citation URIs.

Resources