Skip to main content
Glama

Artic Get Artist

artic_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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": 1234
    },
    "name": "artic_get_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesARTIC artist ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / oneOf
      Added 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"
      +        ]
      +      },
      +      "found": {
      +        "description": "Present and true on an answer; a miss is the found:false branch.",
      +        "enum": [
      +          true
      +        ],
      +        "type": "boolean"
      +      },
      +      "id": {
      +        "description": "Artist ID",
      +        "type": "number"
      +      },
      +      "name": {
      +        "description": "Artist name",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "description": "A miss or an unavailable upstream: found:false with a reason and a hint (the shape check-found-false-schemas.mjs expects).",
      +    "properties": {
      +      "found": {
      +        "enum": [
      +          false
      +        ],
      +        "type": "boolean"
      +      }
      +    },
      +    "required": [
      +      "found"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties
      Removed value: -{
      -  "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"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "id",
      -  "name"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "artwork_ids"
      -]New value: +[
      +  "id",
      +  "name"
      +]
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully carried by structured data. The description's only behavioral contribution is that returned artwork entries are 'linked artwork IDs' rather than full artwork objects — a hint that a follow-up lookup may be needed, but it is not made explicit.

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?

Two tight sentences, with the action and scope front-loaded before the return summary. The second sentence is mildly redundant with the output schema but is short enough to earn its place as a quick scan.

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 one-parameter read tool with full schema coverage, complete annotations, and an output schema, almost nothing is missing. The only gap is that it does not clarify the ID's provenance or that artwork results are references requiring artic_get_artwork.

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 required parameter with 100% schema description coverage ('ARTIC artist ID'), so the schema already does the work. The description's 'by ID' adds no format, range, or sourcing detail beyond that.

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?

Specific verb plus resource plus enumerated fields; distinguishable from the sibling artwork lookup tools.

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?

Usage is only implied: the 'by ID' phrasing signals that the caller must already hold an ARTIC artist ID, but the description never says where to obtain one or when to reach for this instead of a search tool. No exclusions or preconditions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.