Skip to main content
Glama

artic

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 declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, and the description adds rich behavioral context: multi-source fanout, USPTO sunset soft-fail, resolved:false behavior for private companies, empty sections meaning real 'no data', and sources_used/sources_failed semantics. No contradiction exists.

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 packed and front-loaded with user-phrase examples. Each section contributes distinct behavioral or return information, and the semicolon-separated structure makes the multi-source output easy to scan. A bit of redundancy exists, 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?

Despite having no output schema, the description enumerates every major return section, the source list, input normalization rules, failure modes, and the meaning of empty results. An agent can accurately predict invocation semantics and interpret output without needing additional documentation.

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 documents both parameters, so baseline is 3; the description adds value by giving concrete examples ('AAPL', '0000320193', 'Moderna'), clarifying that 'type' values are interchangeable, and explaining that names resolve via SEC EDGAR company-name matching.

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 an explicit purpose: produce a full cross-source profile of a US public company in one parallel call, and leads with concrete trigger phrases like 'Tell me about X' and 'brief me on Tesla.' It clearly differentiates from sibling single-pack lookups by positioning itself as the holistic alternative.

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 guidance: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also indicates what happens for private companies and notes that both 'company' and 'ticker' inputs are accepted, making routing decisions straightforward.

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

All artic 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.9/5.0
Disambiguation4/5

Most tools are carefully delineated with explicit use-case guidance; ask_pipeworx, ask_pipeworx_grounded, and deep_research are clearly separated by depth and grounding. The main weak spots are ask_pipeworx_beta, which is a current functional duplicate of ask_pipeworx, and the several prediction-market/company-research tools that still require careful reading to pick correctly.

Naming Consistency4/5

Names are uniformly snake_case and mostly command-like, with coherent families such as polymarket_*, ask_pipeworx_*, get_art*, subscribe/unsubscribe, and remember/recall/forget. The pattern is not strictly verb_noun throughout, since noun phrases like entity_profile, pipeworx_trending, and recent_changes appear, but the inconsistency is minor and readable.

Tool Count2/5

35 tools is well past the 25+ threshold for a single MCP server, and the set bundles Art Institute lookups, Pipeworx data research, prediction-market analysis, memory, subscriptions, and website utilities into one place. Many tools earn their keep individually, but the overall toolbox feels bloated and poorly scoped.

Completeness3/5

The Pipeworx, memory, and subscription subgroups have decent lifecycle coverage: remember/recall/forget and subscribe/unsubscribe/listsubscriptions/recent_alerts form coherent loops. But relative to the 'artic' server name, the Art Institute surface is thin—there is no artist search and no exhibition-detail tool—and the unrelated embedded domains prevent the set from feeling complete for any one clear purpose.

Resources