Artic

Get Artist

get_artist

Read-onlyIdempotent

Get an artist's biography and their artworks by ID. Returns name, birth/death dates, bio text, and linked artwork IDs.

Input Schema

Name	Required	Description	Default
`id`	Yes	ARTIC artist ID

Output Schema

Name	Required	Description
`id`	Yes	Artist ID
`name`	Yes	Artist name
`birth_date`	No	Birth year or date
`death_date`	No	Death year or date
`artwork_ids`	Yes	IDs of artworks by this artist
`description`	No	Artist biography or description

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": 1234
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "artwork_ids": {
+      "description": "IDs of artworks by this artist",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "birth_date": {
+      "description": "Birth year or date",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "death_date": {
+      "description": "Death year or date",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Artist biography or description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Artist ID",
+      "type": "number"
+    },
+    "name": {
+      "description": "Artist name",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "artwork_ids"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 12, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "id": 1234
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "artwork_ids": {
-      "description": "IDs of artworks by this artist",
-      "items": {
-        "type": "number"
-      },
-      "type": "array"
-    },
-    "birth_date": {
-      "description": "Birth year or date",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "death_date": {
-      "description": "Death year or date",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "description": {
-      "description": "Artist biography or description",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "id": {
-      "description": "Artist ID",
-      "type": "number"
-    },
-    "name": {
-      "description": "Artist name",
-      "type": "string"
-    }
-  },
-  "required": [
-    "id",
-    "name",
-    "artwork_ids"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "artwork_ids": {
+      "description": "IDs of artworks by this artist",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "birth_date": {
+      "description": "Birth year or date",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "death_date": {
+      "description": "Death year or date",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Artist biography or description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Artist ID",
+      "type": "number"
+    },
+    "name": {
+      "description": "Artist name",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "artwork_ids"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "id": 1234
+  }
+]
```
First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive hints. The description adds valuable context about what specific data is returned (name, dates, bio, artwork IDs), going beyond 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?

A single, direct sentence that promptly states the resource, scope, and return content without any filler or redundancy.

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 one well-defined parameter, an output schema, and comprehensive annotations, the description covers all necessary context. It is complete and unambiguous for an agent to invoke.

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 parameter 'id' is fully described in the schema as 'ARTIC artist ID', and the description simply repeats 'by ID' without adding new semantic information. Schema coverage is 100%, so the description does not need to compensate.

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 states the tool gets an artist's biography and artworks by ID, which is specific and distinguishes it from sibling tools like get_artwork and get_exhibitions.

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 'by ID' implies when to use the tool (when you have an artist ID), but it does not explicitly mention alternatives or when not to use it, lacking the clear differentiation of a 4 or 5.

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

All Artic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Get Artist

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources