Artbook Society — Public Catalog

Server Details

Read-only access to the Artbook Society published catalog: books, artists, editors and events.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 22 days
Last Tested: 2026-10-28 17:59
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A3.8/5.0

Scored 2026-10-24 00:55 across 5 tools

Disambiguation5/5

Each tool targets a distinct resource and action: three single-entity getters (artist, editor, product), one event lister, and one product search. There is no realistic way to confuse them, since search_products is explicitly scoped to books/artbooks while list_events is scoped to events.

Naming Consistency5/5

All names follow a clean verb_noun snake_case pattern: get_artist, get_editor, get_product, list_events, search_products. The mix of get/list/search verbs is meaningful and consistent with the operations rather than arbitrary.

Tool Count4/5

Five tools is lean but defensible for a narrow read-only public catalog surface, with each tool earning its place. It sits at the low end of the ideal range, so any expansion of the domain would quickly need more tools.

Completeness3/5

get_artist and get_editor require numeric ids, but there is no list_artists, list_editors, or artist search to discover those ids, and no get_event counterpart to list_events. Product coverage is solid via search_products, but the artist/editor paths are dead ends for discovery.

Available Tools

5 tools

get_artistGet artist profileB

Read-onlyIdempotent

Inspect

Fetch full public details for a single artist by their numeric id.

Name	Required	Description	Default
`id`	Yes	Numeric artist id.

Output Schema

Name	Required	Description
`id`	No
`url`	No
`name`	No
`image`	No
`biography`	No
`specialties`	No

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered. The description adds one useful bit beyond that: the result is the "full public details" view, implying complete but publicly-scoped data. It does not mention auth requirements, rate limits, or error behavior for a missing id.

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?

One sentence, zero filler, with the action, scope, and key all front-loaded. Nothing to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and this is a trivial single-parameter read. The only omission is guidance on behavior when the id does not resolve to an artist, which is minor for a tool of this complexity.

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?

Schema description coverage is 100% and the single id parameter is fully documented there as "Numeric artist id." The description's "by their numeric id" merely restates the schema, adding no format, range, or validity detail beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Fetch full public details for a single artist") plus the lookup key (numeric id), which is enough to distinguish it from the resource-oriented siblings get_editor and get_product. It stops short of explicitly contrasting itself with any sibling, but the single-resource scope is unambiguous.

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

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "single" implies this is the direct-lookup path rather than a list or search, but the description never states when to use this versus a search tool or what preconditions apply. No alternatives or exclusions are named, so usage must be inferred.

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

get_editorGet publisher profileA

Read-onlyIdempotent

Inspect

Fetch full public details for a single editor by their numeric id.

Name	Required	Description	Default
`id`	Yes	Numeric editor id.

Output Schema

Name	Required	Description
`id`	No
`url`	No
`logo`	No
`title`	No
`website`	No
`biography`	No

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds only the mild nuance that returned data is 'public', with no detail on missing-id behavior or error handling, so it adds modest value on top of the annotations.

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?

One short sentence, front-loaded with the verb and resource, with no filler. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The only remaining gap is guidance on invalid or unknown ids, which is minor for a single-id lookup.

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?

Schema description coverage is 100% and there is a single documented 'id' parameter, so the schema already carries the semantics. The description restates 'numeric id' but adds no format, range, or sourcing guidance beyond it — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Fetch) and resource (public details for a single editor) scoped to one numeric id, which cleanly distinguishes it from the search/list siblings. It does not, however, explicitly contrast itself with the structurally similar get_artist and get_product siblings.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'single editor by their numeric id' implies the usage context (you already have an id and want one entity), but no when-to-use conditions, prerequisites, or named alternatives are given. Usage is inferred rather than stated.

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

get_productGet book detailsA

Read-onlyIdempotent

Inspect

Fetch full public details for a single published product by its numeric id.

Name	Required	Description	Default
`id`	Yes	Numeric product id.

Output Schema

Name	Required	Description
`id`	No
`url`	No
`isbn`	No
`image`	No
`price`	No
`title`	No
`author`	No
`editor`	No
`currency`	No
`versions`	No
`description`	No

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds scoping context ('published', 'public details' only), which tells the agent unpublished/internal fields are excluded, but it says nothing about error behavior for missing or unpublished ids.

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?

A single front-loaded sentence with no filler, stating verb, resource, scope and key before any subordinate clause. It is efficient, though the title's 'book details' framing versus the description's 'product' wording introduces minor terminological drift.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required parameter, full schema coverage, an output schema covering return values, and annotations covering the safety profile, the description only needs to establish scope — and it does so via 'published' and 'public'. Nothing essential for a correct call is missing, though the relationship to search_products remains unstated.

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?

Schema coverage is 100% with a single integer 'id' parameter already documented in the schema. The description only restates that the id is numeric, adding no format, range, or example semantics beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (Fetch) and resource (full public details for a single published product) plus the lookup key (numeric id), so the agent knows exactly what it returns. It does not, however, contrast itself with the sibling search_products, which is the main ambiguity for an agent choosing between them.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'A single published product' implies the retriever-by-id use case and implicitly excludes bulk or unfiltered listing, hinting that search_products is the alternative for discovery. But no explicit when-to-use/when-not-to-use statement or sibling reference is given, so the guidance remains inferred rather than stated.

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

list_eventsList upcoming eventsA

Read-onlyIdempotent

Inspect

List published upcoming Artbook Society events, soonest first.

Name	Required	Description	Default
`limit`	No	Maximum number of events (default 10, max 20).

Output Schema

Name	Required	Description
`results`	No	Published events.

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the filtering semantics — only published events, only upcoming ones — and the guaranteed sort order, both of which the annotations do not convey. It stops short of describing pagination behavior, but with an output schema present that gap is minor.

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?

A single sentence that leads with the action and resource, then the scope qualifiers and ordering. No padding, no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple filtered list tool with full annotation coverage and an output schema, the description supplies the scope and ordering an agent needs to call it correctly. It could be slightly stronger by noting the result cap behavior, but 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?

There is a single optional parameter whose schema entry is fully documented (default 10, max 20), giving 100% schema coverage. The description adds nothing about the limit parameter, so the baseline 3 applies.

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 gives a specific verb (List), a specific resource (published upcoming Artbook Society events), and even the ordering (soonest first). The sibling tools operate on entirely different resources (artists, editors, products), so there is no ambiguity to resolve.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The filters 'published' and 'upcoming' implicitly tell the agent this is for browsing future public events, but the description never states when to prefer this tool over alternatives or what conditions exclude its use. Usage is inferred rather than declared.

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

search_productsSearch booksA

Read-onlyIdempotent

Inspect

Search published books and artbooks on Artbook Society. Every keyword must match the title, subtitle, description, an author or contributor, the publisher or the edition type. Optional filters: price range, signed, numbered, limited edition, language.

Name	Required	Description
`limit`	No	Maximum number of results (default 10, max 20).
`query`	No	Keywords (at most 8), in English or French. Each keyword must match. Optional when a filter is given.
`signed`	No	Only signed copies.
`language`	No	Language of the text, ISO 639-1 code (for example fr or en).
`numbered`	No	Only numbered copies.
`max_price`	No	Maximum price in the currency shown in results.
`min_price`	No	Minimum price in the currency shown in results.
`limited_edition`	No	Only limited or collector's editions.

Output Schema

Name	Required	Description
`results`	No	Matching published products.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds a genuinely non-obvious behavioral trait: match is conjunctive across title, subtitle, description, contributor, publisher and edition type — an AND across many fields, unlike typical OR keyword search.

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?

Two sentences, zero waste: the scope and matching rule come first, then the filter inventory. Nothing repeats the schema verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and rich annotations, the description needs only to explain search semantics — which it does. It omits result ordering and the behavior of an empty query with no filters, minor gaps for an 8-parameter, all-optional tool.

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 baseline is 3, but the description goes beyond the schema by explaining what the query string is actually matched against — field coverage the query parameter's own description does not supply. It also names the filter dimensions as a coherent set rather than leaving the agent to infer that price/signed/numbered/limited/language are refinements.

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?

States a specific verb (search) plus the resource (published books and artbooks on Artbook Society), and the query-matching semantics make the retrieval model unambiguous. The 'search' framing cleanly separates it from the singular get_product / get_artist / get_editor siblings.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for finding books by keyword or by the listed filters, but it never states when to choose it over get_product (single-item lookup) or what to do with the IDs a search returns. No exclusions or prerequisites are given; usage is inferred rather than directed.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateOct 22, 2026

Changedsearch_products12 fields changed

addedInput schema / properties / language

Added value: +{
+  "description": "Language of the text, ISO 639-1 code (for example fr or en).",
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}

addedInput schema / properties / limited_edition

Added value: +{
+  "description": "Only limited or collector's editions.",
+  "type": "boolean"
+}

addedInput schema / properties / max_price

Added value: +{
+  "description": "Maximum price in the currency shown in results.",
+  "maximum": 1000000,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / min_price

Added value: +{
+  "description": "Minimum price in the currency shown in results.",
+  "maximum": 1000000,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / numbered

Added value: +{
+  "description": "Only numbered copies.",
+  "type": "boolean"
+}

changedInput schema / properties / query / description

Previous value: -"Text to search for in product titles, author names or contributor names."New value: +"Keywords (at most 8), in English or French. Each keyword must match. Optional when a filter is given."

addedInput schema / properties / query / maxLength
```
Added value: +200
```
addedInput schema / properties / query / minLength
```
Added value: +1
```

addedInput schema / properties / signed

Added value: +{
+  "description": "Only signed copies.",
+  "type": "boolean"
+}

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```
addedOutput schema / properties / results / items / properties / edition_type
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / results / items / properties / editor

Added value: +{
+  "properties": {
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

1 tool updateOct 15, 2026

Changedget_product1 field changed

addedOutput schema / properties / versions

Added value: +{
+  "items": {
+    "properties": {
+      "available": {
+        "type": "boolean"
+      },
+      "name": {
+        "type": "string"
+      },
+      "price": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

1 tool updateOct 6, 2026

Changedsearch_products1 field changed

changedInput schema / properties / query / description

Previous value: -"Text to search for in product titles."New value: +"Text to search for in product titles, author names or contributor names."

5 tool updatesOct 6, 2026
- First observedget_artist
- First observedget_editor
- First observedget_product
- First observedlist_events
- First observedsearch_products

Related MCP Connectors

SHAR Public Knowledge MCP B
com.sharprod
Anonymous read-only access to source-backed public SHAR Production knowledge.
Open Data Documentation Access Search
1
https://mcp.sharprod.com/public
The Family Almanac — parenting library, guide metadata, and magazine A
com.thefamilyalmanac
Read-only access to The Family Almanac's parenting-focused book library, grounded guide metadata...
Education & Learning Tools
51
https://thefamilyalmanac.com/api/mcp
Shelfclub A
app.shelfclub
Search a catalog of 1.7 million books and find books by mood, vibe, pace or genre. Read-only.
Search Entertainment & Media
61
https://mcp.shelfclub.app/mcp
Basedworld Agent HQ A
dev.fly.basedworld
Find public creator tools, work and conversation. Read-only; no wallet, posting or payment.
E-commerce & Retail Search
91
https://basedworld.fly.dev/mcp

Related MCP Servers

catalogue-api
Search Open Data Research & Data
ibraheemmawwal
F
license
Not graded
quality
A
maintenance
Provides a read-only API over a book catalogue, offering tools to search books, retrieve book details and series, and inspect provenance and source agreement data.
Updated 2 months ago (2026-08-23 10:21 UTC)
-
ai.familyofficeknowledgegraph/
Knowledge & Memory Open Data Search
Agentic-Private-Office
A
license
Not graded
quality
D
maintenance
Provides read-only access to the Family Office Knowledge Graph, enabling resolution of family offices, retrieval of public records with provenance, and listing of events, aliases, and nodes.
Updated 10 days ago (2026-10-18 16:16 UTC)
MIT
reknihy-mcp
E-commerce & Retail Search
birosrichard
A
license
A
quality
C
maintenance
Enables read-only search and retrieval of the public Reknihy.cz book catalog, including filtering, sorting, ISBN lookup, category browsing, and access to product details such as price, availability, and images.
Updated 2 months ago (2026-09-01 15:58 UTC)
4
ISC
geolens-mcpofficial
Databases Location Services Search
geolens-io
A
license
A
quality
A
maintenance
Read-only access to a self-hosted GeoLens geospatial catalog: dataset search, schemas, GeoJSON features, saved maps, and sandboxed read-only SQL over PostGIS.
Updated 2 days ago (2026-10-27 01:39 UTC)
6
282
Apache 2.0