Skip to main content
Glama
Sign In

Simpler.Asia

by asia.simpler
OverviewDiscussionsAdmin

template.run

[paid: up to $0.66 a run; template.list gives each template's price] Run one media template for this workspace. The product templates (product-shot, product-lifestyle, showcase-video) first read the words printed on the product and answer status needs_label with label_words and nothing charged: show the words to the owner, then call again with the same slots plus label_words set to the confirmed list (the answer's next says exactly how). Images land in the image library (asset_key and url; a download_url when signed links are on). showcase-video makes its still in the call and answers status rendering: the video takes 1 to 2 minutes, so call template.status with the run_id. explainer-voice answers with an MP3 and a WebVTT caption file. price.quoted_micro_usd is the most the run can cost; price.charged_micro_usd is what it did. Refuses: VALIDATION_ERROR (each slot issue named), SIMPLER_MEDIA_INPUT_MISSING / SIMPLER_MEDIA_URL_REFUSED (pass an asset_key, https or data:image), INSUFFICIENT_CREDITS (add credits), the prompt guard's refusals (slot words that name a real person, or sexual or other harmful content), SIMPLER_MEDIA_TEMPLATE_RUNS_UNMIGRATED (templates not switched on yet; nothing charged).

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": {
      "template": "<template>",
      "slots": "<slots>"
    },
    "name": "template.run"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotsYesThe template's slot values by name; template.list names each template's slots (the templates that take a slot are in brackets). Image slots are an asset_key, https URL or data:image URL.
templateYesThe template id (template.list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With only readOnlyHint=false in annotations, the description carries the behavioral burden and does so richly: it discloses paid runs, price caps versus charges, the free label-reading step, asynchronous video timing, output locations, and specific refusal/error conditions.

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 dense but front-loads cost and purpose before the template-specific details. It is appropriately sized for a complex paid orchestration tool, though the long error-code list makes it somewhat heavy.

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?

Given the tool's complexity, the rich schema, and the absence of an output schema, the description supplies enough return behavior: image library outputs, video rendering/status flow, explainer-voice MP3/WebVTT outputs, and billed versus quoted prices.

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 description coverage is 100% and the slot schema already documents template-specific slots, image input formats, and the label_words two-step flow. The description reinforces the workflow but adds little parameter meaning beyond what the schema already provides.

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 uses a specific verb and resource: 'Run one media template for this workspace.' It also names template.list for pricing and template.status for video polling, which distinguishes this tool from its siblings.

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 usage context for product templates, showcase-video polling, and explainer-voice outputs, and it points to template.list and template.status as related tools. It stops short of explicit when-not guidance beyond the listed refusal/error cases.

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

All Simpler.Asia 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