Skip to main content
Glama

Artsmia

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

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

Beyond the readOnly/idempotent annotations, the description discloses valuable behavioral details: the tool fans out across many sources in parallel, returns sources_used/sources_failed, treats empty sections as real no-data results, and returns resolved:false with a notes line for private companies rather than raising a bare failure. This gives the agent an accurate model of what the tool will and will not do.

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 this is justified by the tool's breadth: it covers many data sources, return fields, input forms, and edge cases. It is front-loaded with the main purpose and usage rule, though the dense one-paragraph structure makes scanning harder than it could be with lists or headings.

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 available, the description carries the full burden of explaining return values, and it does so thoroughly: CIK, resolved_from/resolved_to, recent_filings with URIs, fundamentals, patents, contracts, FDA products, hiring, news, LEI, and source success/failure reporting. It also covers the private-company case and input flexibility, so an agent has enough context to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents both parameters thoroughly, including that type accepts company/ticker interchangeably and value accepts ticker, CIK, or company name. The description mostly echoes this same guidance, with minor additions like the private-company resolved:false behavior, which is more about output semantics than parameter meaning.

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 user phrasings and immediately states the core action: full cross-source profile of a US public company in ONE parallel call. It clearly distinguishes this tool from narrower single-pack SEC/XBRL/news lookups and sibling tools like resolve_entity.

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 explicitly says to ALWAYS PREFER this tool over chaining single-pack lookups when the user asks for a holistic view. It also tells the agent what inputs are acceptable, how name resolution behaves, and what happens for private companies, leaving no ambiguity about when and how to invoke it.

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

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

Several tools have heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are described as currently identical, and the polymarket_* family (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread) all target prediction-market analysis with fuzzy boundaries. ai_visibility_check and scan_competitor_ai_presence overlap as well. While some tools are clearly distinct (art search vs memory), the set as a whole requires careful reading to avoid misselection.

Naming Consistency2/5

Tool names follow multiple patterns: verb_noun (search_artworks, resolve_entity, validate_claim), domain_prefixed (polymarket_*, pipeworx_*), and product-style names (ask_pipeworx, bet_research, deep_research). Versioned suffixes like ask_pipeworx_beta and ask_pipeworx_grounded break any unified convention. Even though subgroups are internally consistent, the overall pattern is mixed and unpredictable.

Tool Count2/5

34 tools is on the high side, especially for a server named after an art museum. Only 3 tools actually relate to the Minneapolis Institute of Art, while the rest are a general-purpose data platform, prediction-market analysis, and memory/subscription features. Many of these extra tools are redundant or power-user variations, making the count feel inflated relative to the apparent domain.

Completeness3/5

For the stated art domain, the read-only surface (search, get, department highlights) is functional but thin — no artist browse, exhibitions, or advanced filtering. The broader data tools are comprehensive in themselves, but their presence distracts from the core domain and creates confusion about the server's intended purpose. The art coverage is adequate for basic queries but lacks depth expected from a dedicated museum collection API.

Resources