Skip to main content
Glama
Sign In

framesail

by com.framesail
OverviewDiscussions(1)Admin

Generate for the channel style

style_generate
Destructive

analyze: read the references again and rewrite art_style, narrative_style, director_style and text_style, replacing hand edits.

template: render one of the style's two template images. Reference images render on them (characters on the character template, environments and objects on the environment one) and segment images fall back on them, so finish both before any reference image. An existing one is refused unless replace=true: replacing it changes the look of everything rendered after.

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": {
      "action": "<action>",
      "channel_id": "<channel_id>"
    },
    "name": "style_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel id (get_generation_options); omit for the saved choice
actionYesanalyze; template: template_type
replaceNotemplate: true only when the user asked for a new image (or agreed to render a stale one again)
settingsNoModel settings: keys of its settings_schema
channel_idYesThe channel whose style this is
template_typeNotemplate: which template image; run once for each
editable_sectionsNoTemplate prompt section overrides, keyed by section id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

The description adds substantial context beyond the annotations: analyze replaces hand edits, template images must be completed in order, existing templates are refused unless replace=true, and replacing one changes how everything rendered afterward looks. This is exactly the kind of destructive consequence an agent needs to know.

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 description is compact and front-loads the two action modes with labels. It is dense but nearly every sentence carries operational information, with only minor room for a clearer top-level lead sentence.

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 seven-parameter, two-action destructive generation tool, the description covers the important workflow, replacement risk, and output intent. Some details such as editable_sections and model override behavior are left entirely to the schema, but the description remains sufficient for correct invocation.

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 100%, so the structured schema already carries most parameter semantics. The description still adds meaningful action-level context, especially for analyze versus template and the sequencing of template_type, going beyond the enum labels.

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?

The description clearly specifies what each action does: 'analyze' rewrites four style fields and 'template' renders one of two template images. It is much more specific than the generic tool name, though it does not explicitly distinguish this tool from sibling style_edit or style_read.

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 clear operational guidance for each action, including that both templates must be finished before any reference image and that replace=true is only for a new image or an agreed stale rerender. It does not explicitly state when to choose style_generate over style_edit or style_read.

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

All framesail toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources