Skip to main content
Glama

Fbi Artcrimes

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?

Annotations already declare read-only, idempotent, and non-destructive behavior, and the description adds substantial behavioral context: fan-out across many sources, sources_used/sources_failed reporting, empty sections meaning genuine 'no data', a GDELT→GNews fallback, and private companies returning resolved:false with a notes line rather than a bare failure. This deeply helps an agent interpret partial results.

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 front-loaded with user triggers and the core preference, and nearly every sentence carries necessary information. It is dense and somewhat run-on with heavy parentheticals; structuring the sources and return fields as bullets would improve scanability, but nothing feels wasteful.

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?

For a complex multi-source tool with no output schema, the description covers input variants, output highlights, source failure semantics, fallback behavior, private-company edge cases, and name resolution. An agent has enough context to invoke it correctly and interpret unusual responses.

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 documents both parameters with 100% coverage, so the schema carries much of the load. The description nonetheless adds useful semantics: concrete examples, emphasis on zero-padded CIKs, interchangeability of ticker/CIK/name for both type values, and the private-company resolution behavior.

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 clearly identifies the resource as a 'full cross-source profile of a US public company' and pairs it with concrete user triggers like 'Tell me about X' and 'company profile for Microsoft'. It also distinguishes the tool from narrower lookups by stating it should be preferred over chaining single-pack SEC/XBRL/news lookups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/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 lookups when the user asks for a holistic view, which is strong when-to-use guidance. However, it does not name or route to sibling tools such as resolve_entity or compare_entities, so the alternative selection guidance is not fully complete.

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

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

ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers (beta is currently exactly the same as stable), and the Polymarket tools (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research) all scan or price prediction-market opportunities with fuzzy boundaries. Other clusters like memory and subscriptions are clear, but enough overlap remains that an agent can easily misroute a query.

Naming Consistency3/5

Most names are readable snake_case and many follow a verb_noun shape (list_art_crimes, resolve_entity, validate_claim), but the set also contains noun-phrase names (entity_profile, recent_alerts, pipeworx_feedback, deep_research) and brand-prefixed composites (polymarket_kalshi_spread, ask_pipeworx_beta). This is mixed but still scannable; there is no outright convention chaos.

Tool Count2/5

33 tools exceeds the 25+ threshold and is bloated for a server whose name promises FBI art crimes—only two tools relate to that name. Even treated as a Pipeworx platform, the sprawl makes the tool surface harder to navigate than necessary.

Completeness2/5

For the nominal art-crime domain, only list_art_crimes and get_art_crime exist, with no category search, statistics, or art-crime alerting, so an agent expecting art-crime workflows hits dead ends. The unrelated Pipeworx functionality is broadly covered, but that does not make the set complete for its stated server purpose.

Resources