Skip to main content
Glama

Fbi Artcrimes

by io.github.pipeworx-io

List Art Crimes

list_art_crimes
Read-onlyIdempotent

Browse or search the FBI National Stolen Art File — stolen and missing artworks under active FBI art theft investigations. Returns artwork UIDs, titles, descriptions, maker/artist, materials, measurements, period, and a thumbnail image URL. Filter by title or maker substring. Use page to paginate. Pass a UID into get_art_crime for the full record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1).
makerNoFilter by artist/maker substring (e.g., a painter or publisher).
titleNoFilter by title substring (e.g., a work or object name).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety and idempotency. The description adds beyond these by clarifying that only active investigations are included, listing returned fields, and noting the thumbnail URL limitation. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with no filler. It opens with the core purpose, follows with return fields, then provides essential filter and pagination usage, all in a compact and easily parsed structure.

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 simple three-parameter list endpoint, the description covers scope, returned fields, filtering, pagination, and points to get_art_crime for fuller records. With no output schema, the return-field list is sufficient, and annotations cover idempotency and read-only behavior, so nothing essential is missing.

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?

All three parameters have schema descriptions with 100% coverage, so the schema already explains page, maker, and title. The description restates the substring filtering semantics but adds no significant new meaning beyond what the schema provides, so baseline 3 is appropriate.

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 names a specific verb and resource — browse/search the FBI National Stolen Art File — and enumerates the exact fields returned. It clearly distinguishes list_art_crimes from get_art_crime by noting that the latter provides the full record when a UID is passed.

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 operational guidance: filter by title or maker substring, use page for pagination, and pass a UID to get_art_crime for full records. This provides direct, actionable usage context that routes the agent to the correct sibling tool.

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