Skip to main content
Glama

list_styles

Read-onlyIdempotent

List every built-in Dinoctor animation style with its ID, name, purpose, and depth, marking the project's current style so you can pick one for library details, a new project, or a style switch.

Instructions

Read-only: every built-in Dinoctor style with its id, name, what it's for and its depth (2D, 2.5D or real 3D), with the project's current style marked. Use an id with library (what it offers), new_project or set_style. The person's own styles are listed by my_styles.

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 and destructiveHint=false, so 'Read-only' earns little credit. However, with no output schema the description usefully discloses the shape of the result set (per-style id, name, purpose, depth enum of 2D/2.5D/3D) and that the project's current style is flagged, which is real behavioral detail beyond the annotations.

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 tight sentences, each carrying unique information: result shape, downstream usage, and the sibling delegation. The scoping detail is front-loaded with no filler.

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 parameters, no output schema and annotations covering the safety profile, the description supplies everything an agent needs: what comes back, how ids are consumed, and where to go for user styles.

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?

Zero parameters, so the baseline is 4; there is nothing to disambiguate. The only implicit input is project context for the current-style marker, which is hinted at by 'the project's current style'.

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+resource (list every built-in Dinoctor style) and enumerates the returned fields (id, name, purpose, depth) plus the current-style marker. It explicitly distinguishes built-in styles from the person's own styles, which my_styles covers.

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?

Tells the agent what to do with the returned ids (library, new_project, set_style) and routes the user-owned-style case to my_styles, so the selection boundary is explicit rather than inferred.

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