Skip to main content
Glama

Get a character sheet

get_character_sheet
Read-onlyIdempotent

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 (23 credits for 5 images of a person, 11 for an animal or mascot). Free. Use this before create_character_sheet and tell the human the price. Characters are fictional adults (or animals / mascots), AI-generated: no real or famous people, no children or anyone who looks under 18, no sexual content, no logos or protected characters (refused with CONTENT_POLICY, nothing charged). Everything made here is AI-generated and labelled as such. Requires the "video:read" 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>"
    },
    "name": "get_character_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYesA series id from list_series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, and the description adds substantial behavior beyond them: the call is free, a new sheet costs 23 credits (5 images of a person) or 11 (animal/mascot), a series is capped at 3 sheets, content-policy violations are refused with CONTENT_POLICY and nothing is charged, and the "video:read" scope is required. These are exactly the cost, quota, and authorization facts an agent needs before invoking or recommending it.

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?

Content is front-loaded with the read purpose and returned fields, and every clause carries information (pricing, quota, policy, scope). The first sentence is long and comma-chained, bundling return shape, quota, and pricing together, which slightly hurts scanability 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?

There is no output schema, and the description compensates by enumerating the returned fields (image ids, views, urls, chosen sheet/image, remaining quota, price). Combined with scope, cost, and policy-refusal behavior, an agent has everything needed to call it and interpret the result.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself pointing to list_series as the id source. The description adds little beyond restating that the id selects "one of your series" and that sheets are per-series, 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?

States a specific verb and resource ("Read the character sheets of one of your series") and then enumerates exactly what a sheet contains: images with id/view/url, which sheet and image are chosen, remaining sheet quota, and per-sheet price. This lets an agent distinguish it from create_character_sheet and the select/image siblings without opening any schema.

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?

Explicitly sequences the call: "Use this before create_character_sheet and tell the human the price," which names the downstream alternative and the human-facing action. It does not cover when the call can be skipped (e.g., sheet already known from a prior response), so it falls short of full when/when-not coverage.

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