Skip to main content
Glama

List options and prices

autoshort_list_options
Read-onlyIdempotent

Lists accepted options and prices—voices, styles, niches, themes, aspect ratios, durations, providers, scene costs—and the tool for each, so you can choose values instead of guessing enums. Free.

Instructions

Every option and price the tools accept, from the live constants: voices for a language (premium flag + extra credits), art styles (PRO flag), niches, caption themes, aspect ratios, the durations each tool allows, video providers for the plan, motion-clip / hero-scene prices — and for each, which tool lets you choose it. Use it instead of guessing an enum. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "autoshort_list_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoVoice language (default "en").

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 cover read-only, idempotent, non-destructive and closed-world, so safety is settled. The description adds genuinely new behavior: the values come from live constants (not a frozen doc), it exposes premium/PRO flags and extra-credit pricing, and it states the call is free — important context next to paid sibling tools like buy_credits and generate_motion_clip. It does not describe response shape or size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense catalogue sentence front-loads what the tool returns, followed by two short sentences giving the usage rule and the cost. Every clause carries concrete information (which option families, what flags accompany them), and nothing is redundant with the annotations or schema.

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 carries the burden of describing returns and does so thoroughly by listing the option families plus the accompanying price/flag data and the tool mapping. It is nearly complete for a one-optional-param read tool, with only minor gaps around the structure of the returned data.

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 optional parameter exists and schema coverage is 100%, so the schema already documents language and its default. The description's phrase 'voices for a language' implies the parameter scopes the voice list, which is a small but real addition of meaning beyond the schema.

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 names the exact resource — every option and price the tools accept — and enumerates the concrete categories returned (voices, art styles, niches, caption themes, aspect ratios, durations, providers, motion-clip/hero-scene prices). It also states the extra payload ('which tool lets you choose it'), so an agent knows this is a discovery/catalog tool rather than a single-list tool like the sibling list_* calls.

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?

'Use it instead of guessing an enum' is an explicit, actionable directive that tells the agent to call this before feeding option values into other tools. 'Free' further lowers the cost of calling it. It stops short of disambiguating against overlapping siblings such as autoshort_list_niches, which the description also claims to cover.

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