Skip to main content
Glama

httpcat

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?

The description discloses behaviors beyond the annotations: parallel fan-out across multiple sources, soft-fail for the USPTO sunset, empty-section semantics ('an empty section is a real no data, not a bug'), resolution behavior, and the meaning of sources_used/sources_failed. It also reveals internal details like URI format and sort order, which the annotations do not cover.

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 quite long, but nearly every sentence carries functional load: examples, source list, return-field semantics, edge-case handling, and input flexibility. It front-loads purpose and usage, then packs details in a readable sequence. Slightly redundant phrasing like 'either way' and the FDA caveat could be trimmed, but the length is justified by the tool's complexity.

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?

Given the tool has two parameters, a broad multi-source scope, and no output schema, the description covers everything an agent needs: accepted input shapes, return-field semantics, failure modes, source-specific quirks, and resolution handling. The private-company behavior and the 'empty is real no-data' clarification prevent common misinterpretations. No critical operational detail is missing.

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%, so the baseline is 3. The description further enriches both parameters by clarifying that type accepts 'company' or 'ticker' interchangeably and that value can take a ticker, zero-padded CIK, or name shape, plus resolution caveats and the private-company fallback. It exceeds the schema's descriptions with concrete examples and behavioral nuance.

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 states a specific verb-resource pair: 'full cross-source profile of a US public company in ONE parallel call' and immediately differentiates from sibling tools by naming the alternative strategy it replaces ('ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups'). It also provides varied example phrasings, making the intended invocation unmistakable.

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?

The description gives explicit when-to-use conditions (user asks for a holistic view) and explicit exclusions ('a private company (no CIK/ticker) returns resolved:false with an explicit notes line'). It names the preferred alternative pattern (single-pack lookups) and tells the agent not to chain them, leaving no ambiguity about when to choose this tool.

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

All httpcat 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.5/5.0
Disambiguation2/5

Several tools have overlapping or near-identical purposes, e.g., ask_pipeworx and ask_pipeworx_beta are explicitly described as currently equivalent, and polymarket_arbitrage, polymarket_edges, and bet_research all target prediction-market opportunities. Descriptions help somewhat, but boundaries remain fuzzy for agents.

Naming Consistency2/5

Tool names follow no consistent convention: some are verb-first (get_status_cat, remember), others are noun phrases (entity_profile, deep_research), and many use domain prefixes (ask_pipeworx, polymarket_*, pipeworx_feedback). While snake_case is maintained throughout, the structural pattern is mixed and unpredictable.

Tool Count2/5

At 33 tools, the server is well beyond the typical well-scoped range (3-15). The count is inflated by multiple overlapping meta-tools and unrelated utility groups (HTTP cats, Pipeworx research, prediction markets, memory, subscriptions), making the set feel bloated rather than focused.

Completeness2/5

The server name 'httpcat' implies HTTP status-cat functionality, but only 2 of 33 tools serve that purpose, leaving the named domain largely uncovered. As a general-purpose data server, the collection still has gaps (e.g., no direct trading, no general web search) and appears to be a random assortment of features rather than a coherent product.

Resources