Skip to main content
Glama

Choose the series character image

autoshort_select_character_image
Idempotent

Select a READY character sheet for a series and optionally set its main image, which serves as the starting point for generating a motion clip from that character.

Instructions

Choose which character sheet a series uses and which of its images is the main one. The main image is what autoshort_generate_motion_clip starts from when you pass character_id (the sheet id). Only your own READY sheets and their images can be chosen. Free.

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": {
      "seriesId": "<seriesId>",
      "sheetId": "<sheetId>"
    },
    "name": "autoshort_select_character_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdNoAn image id of that sheet to make the main image. Omit to keep the current main image.
sheetIdYesA sheet id from autoshort_get_character_sheet.
seriesIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds that the call is free, that eligibility is limited to your own READY sheets, and what the selected main image feeds into. It does not explain what happens to a previously selected sheet or its images when a different one is chosen, which is the main behavioral gap for a mutation.

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?

Three short sentences, front-loaded with the action and its effect, then eligibility, then cost. No filler or repetition 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 three-parameter mutation with no output schema, the description covers eligibility, cost, and downstream consumption, which is close to sufficient. The remaining hole is replacement semantics: what happens to the prior sheet selection and whether existing clips are affected.

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 67%, so two of three parameters are documented there. The description adds real meaning beyond the schema by mapping character_id used elsewhere to the sheetId parameter, which removes a likely naming confusion; only seriesId remains entirely undocumented across both.

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: choose which character sheet a series uses and which of its images is the main one. This clearly separates it from sibling tools that create or fetch sheets (autoshort_create_character_sheet, autoshort_get_character_sheet) because it is an assignment operation on a series, not a sheet-producing one.

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

Usage Guidelines4/5

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

It gives a prerequisite ("Only your own READY sheets and their images can be chosen") and downstream context (the main image is what autoshort_generate_motion_clip starts from when character_id is passed). It doesn't state when not to use it or name a concrete alternative for changing only the sheet versus only the image, so it falls short of full routing guidance.

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