Skip to main content
Glama

Select a character image

select_character_image
Idempotent

Choose which character sheet a series uses and which of its images is the main one. The main image is the reference every still of an episode is made from. Only your own READY sheets and their images can be chosen. Free. Requires the "video:create" scope.

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": "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 get_character_sheet.
seriesIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations (readOnly=false, destructive=false, idempotent=true) with cost ('Free.'), an auth requirement ('Requires the "video:create" scope.'), and a validity gate on input state (sheets must be READY and owned). It does not say what happens when an invalid or non-READY sheet is supplied, or whether a replaced main image can be restored, which are the remaining behavioral gaps.

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, each earning its place: purpose and payoff first, then the eligibility constraint, then cost and scope. No repetition of the title or schema fields, and the most decision-relevant constraint is not buried.

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 only three parameters, existing annotations, and no output schema, the definition covers purpose, eligibility, cost, and permission requirements adequately. The only shortfall for a mutation tool is the absence of failure behavior when a sheet is not READY or not owned.

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%, with the undescribed parameter being seriesId; the description compensates by framing the operation as pairing a series with a sheet, and by adding validity constraints on sheetId/assetId that the schema does not state. It still does not clarify whether assetId must belong to the given sheet beyond the schema's brief note.

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: choosing which character sheet a series uses and which image is its main one, then explains what the main image means downstream ('the reference every still of an episode is made from'). That downstream consequence distinguishes the effect from sibling tools like get_character_sheet or create_character_sheet, though it never explicitly names an alternative tool to contrast against.

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?

Gives a concrete precondition ('Only your own READY sheets and their images can be chosen') and clarifies the optional-parameter case ('Omit to keep the current main image'). It does not state when-not to use this tool or name the sibling used to obtain a sheet id, though the schema description partially covers the latter.

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.

Resources