Skip to main content
Glama

list_styles

Read-onlyIdempotent

Lists the 10 Cuecaps caption styles with IDs, names, and visual appearance so users can pick a caption style or pass its ID to caption_video or studio_link.

Instructions

Lists the 10 Cuecaps caption styles, each with the id to pass as style to caption_video or studio_link, its name and how it looks. The list is fixed and needs no key. Call it when the user hasn't picked a style or asks what the styles look like.

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": "list_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds genuinely new behavioral facts beyond those: the list is fixed and requires no key, and it discloses the shape of each entry. It stops short of noting ordering or caching guarantees, so not a 5.

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?

Three short sentences: what it returns, how the result is consumed, and when to call it. No filler, and the actionable trigger is placed last where it reads as the decision rule.

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?

With no output schema, the description compensates by enumerating the fields of each returned style (id, name, appearance) and explaining what the id is for. Nothing needed to invoke or interpret this zero-argument read tool is missing.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no filtering or selection arguments exist by framing the result as a complete fixed list of 10.

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?

Specific verb plus resource ('Lists the 10 Cuecaps caption styles') with the exact payload spelled out (id, name, appearance). It also disambiguates by naming the downstream tools that consume the returned id (caption_video, studio_link), so an agent can place it relative to 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger conditions: 'Call it when the user hasn't picked a style or asks what the styles look like.' That is a concrete when-to-use rule tied to the downstream caption_video/studio_link flow, leaving little to inference.

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