Galatic.ai

Save artist

save_artist

Create an AI artist (no artistId) or update one of the user's artists, and return { artist }. Create needs name; the artistId is made from the name and a taken one is refused (409); referenceImageKey is ignored on create, so set the photo with a second call. Update changes only the fields passed (403 for another user's artist); styleDescriptors replaces the list, and referenceImageKey must be under the user's own gallery prefix (null removes the photo). referenceImageKeys sets the list of reference photo OPTIONS (up to 6, each under the user's gallery prefix) and does not change the active photo. activeReferenceKey switches the active photo and changes the face in the artist's videos, so it must be one of the options or the current photo. artistId comes from list_artists.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "save_artist"
  }
}

Input Schema

Name	Required	Description
`bio`	No
`name`	No	Required to create.
`show`	No
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`artistId`	No	From list_artists. Omit to create.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`creativeBrief`	No
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
`styleDescriptors`	No	Replaces the whole list.
`referenceImageKey`	No	Update only: an S3 key under the user's gallery prefix, e.g. from upload_media.
`activeReferenceKey`	No	Update only: switch the active reference photo. Must be one of referenceImageKeys or the current photo.
`referenceImageKeys`	No	Update only: the reference photo options (S3 keys under the user's gallery prefix, up to 6). Replaces the list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

addedInput schema / properties / activeReferenceKey

Added value: +{
+  "description": "Update only: switch the active reference photo. Must be one of referenceImageKeys or the current photo.",
+  "type": "string"
+}

addedInput schema / properties / referenceImageKeys

Added value: +{
+  "description": "Update only: the reference photo options (S3 keys under the user's gallery prefix, up to 6). Replaces the list.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 6,
+  "type": "array"
+}

Changed4 schema fields changedOct 27, 2026
- addedInput schema / properties / artistId / description
```
Added value: +"From list_artists. Omit to create."
```
- addedInput schema / properties / name / description
```
Added value: +"Required to create."
```
- addedInput schema / properties / referenceImageKey / description
```
Added value: +"Update only: an S3 key under the user's gallery prefix, e.g. from upload_media."
```
- addedInput schema / properties / styleDescriptors / description
```
Added value: +"Replaces the whole list."
```
First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations declare readOnly=false, destructiveHint=false and idempotentHint=false, so the write nature is already known. The description adds real value beyond that: a 409 on a taken name, a 403 for another user's artist, styleDescriptors replacing rather than merging, and activeReferenceKey changing the face in existing videos. However, it does not disclose that repeated identical calls are non-idempotent or what the artist object contains, leaving some behavioral surface to inference.

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?

Front-loaded with the create/update distinction and the return shape, then ordered by parameter importance. It is a dense single block, but each sentence carries a distinct rule or edge case; only the duplicated "referenceImageKey is ignored on create" / "set the photo with a second call" phrasing could be tightened.

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 12-parameter mutation tool with no output schema, the description covers the return value ({ artist }), the two error paths, the create/update split, and the full photo-management lifecycle. Nothing an agent needs to call it correctly is missing, aside from the three plain string fields whose names are self-describing.

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 hardest ambiguity — three near-identically named photo parameters — is fully disambiguated: referenceImageKey sets the photo, referenceImageKeys sets up to 6 options without changing the active photo, activeReferenceKey switches the active photo. styleDescriptors is correctly flagged as a full replacement. The gap is that bio, show, and creativeBrief get no explanation anywhere in the schema or description.

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?

Opens with a specific verb pair and resource: "Create an AI artist (no artistId) or update one of the user's artists, and return { artist }." The create-vs-update discriminator is the artistId, which immediately separates it from list_artists and add_artist_project.

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?

Explicitly states when to create (omit artistId) vs update (pass artistId), tells the agent where artistId comes from (list_artists), and warns that referenceImageKey is ignored on create so a second call is required to set the photo. That is a concrete alternative-path instruction, not just context.

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

All Galatic.ai 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.