Skip to main content
Glama

Read character sheets

autoshort_get_character_sheet
Read-onlyIdempotent

Read a series' character sheets to review each fictional character's AI images, selected sheet/image, remaining sheet allowance, and exact cost of a new sheet before creating one.

Instructions

Read the character sheets of one of your series: each sheet is a set of AI images of one fictional character, its images (id, view, url), which sheet and which image are chosen, how many sheets the series may still make (3 in total), and the exact price of a new sheet (21 credits for 5 images of a person, 10 for an animal or mascot). Free. Use this before autoshort_create_character_sheet and tell the user the price.

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>"
    },
    "name": "autoshort_get_character_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYesA series id from autoshort_list_series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description goes beyond them with operationally important facts the annotations cannot convey: the call is free, the quota is 3 sheets per series, and a new sheet costs 21 credits (person) or 10 (animal/mascot). It does not cover failure modes or how quota exhaustion is signalled, keeping it at 4.

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?

The action and scope are front-loaded in the first clause, and every subsequent phrase contributes a distinct fact (payload contents, quota, price, ordering). It is a single dense run-on sentence, which slightly hurts scannability but wastes no words.

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 no output schema, the description compensates by describing the returned fields (image id, view, url, chosen sheet/image, remaining quota, price). Combined with the free-call note and the pre-creation ordering instruction, an agent has everything needed to call and use this tool correctly.

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?

Schema coverage is 100% and the single seriesId parameter is documented in the schema as coming from autoshort_list_series. The description only implies this via 'one of your series' and adds no format or sourcing detail beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource ('Read the character sheets of one of your series') and then enumerates what a sheet contains: AI images with id/view/url, which sheet and image are selected, remaining sheet quota, and per-sheet pricing. It is plainly distinguishable from the sibling autoshort_create_character_sheet, which it names.

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 explicit ordering guidance ('Use this before autoshort_create_character_sheet') and a concrete instruction to relay the price to the user, which is real usage context. It stops short of a full when/when-not statement (e.g., no guidance on calling it after selection changes), so it is not a 5.

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