Skip to main content
Glama

story_create_asset

Add a character, background or prop to a Story mode project — for ones the script breakdown did not find. Free. With image_url the picture becomes its reference at once (image_url must be a URL returned by upload_asset). Without it the asset has no picture yet: price asset_images with story_quote to have Wandura draw one, or set one later with story_set_asset_image. A name that already exists is refused — edit that asset instead.

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": {
      "project_id": "<project_id>",
      "kind": "<kind>",
      "name": "<name>"
    },
    "name": "story_create_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYes
identityNoShort phrase added to every prompt that uses it. Default = the name.
image_urlNoOptional reference picture: a URL returned by upload_asset.
project_idYes
descriptionNoLooks, age, clothing, mood — what its picture is drawn from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare write (readOnlyHint=false), non-idempotent, non-destructive, so the description's job is to add context — and it does: the operation is free, image_url must be a URL from upload_asset, a duplicate name is refused, and an asset without image_url has no picture until priced or set. It stops short of describing what is returned or whether the project must already exist, but this is well above what the annotations carry.

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 purpose, then cost, then the two image paths, then the error case — a sensible ordering. Fairly dense with clauses, but every sentence carries an operative fact; nothing is padding.

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 no output schema, the description still covers cost, idempotency-adjacent behavior, parameter provenance, and the downstream alternatives for getting an image. The remaining gap is what a successful create yields (e.g. the new asset id) and any project-state prerequisite.

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 only 50%, so the description must compensate, and it does for the highest-risk parameter: image_url's provenance (must come from upload_asset) and immediate effect. It also enumerates the three kind values inline. identity and description are left to the schema, and project_id/name receive no elaboration.

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 (Add) and resource (character/background/prop) scoped to Story mode projects, and the clause 'for ones the script breakdown did not find' separates it from story_update_asset and the script-derived asset flow. An agent can pick this out from siblings without opening the schema.

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?

Explicit routing: use with image_url for an existing reference picture, without it price the drawing via story_quote, or set an image later with story_set_asset_image. It also names the exclusion — a duplicate name is refused and you should edit that asset instead — which is exactly the when-not guidance an agent needs.

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