Skip to main content
Glama
Sign In
aidance-mcp

aidance-mcp

by rocnubie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_styles

Return the canonical list of image-generation styles and presets exposed by AI Dance. Access every available artistic style for image creation.

Instructions

Return the canonical list of image-generation styles or presets the site exposes. (AI Dance)

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.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It clearly implies a read-only operation by saying 'Return', but it does not disclose additional behavioral traits such as caching, rate limits, or whether the list is dynamically generated. For a simple list tool, this is adequate but not rich.

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?

The description is a single sentence that is concise and front-loaded. It includes a clarifying note '(AI Dance)' which adds context without extra fluff. Every word earns its place.

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 has no parameters, no output schema, and a straightforward purpose, the description is fully complete. It states exactly what will be returned and the scope. There is no missing information for an agent to invoke this correctly.

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 has zero parameters, and the schema is empty, which means schema description coverage is effectively 100%. The description adds no parameter details because there are none, and baseline for zero parameters is 4. No additional semantic burden is needed.

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 states a specific verb ('Return') and resource ('canonical list of image-generation styles or presets the site exposes'), which clearly distinguishes it from sibling tools like get_pricing and get_official_links. It is unambiguous about the tool's function.

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?

The description provides clear context: it returns styles/presets for image generation. While it does not explicitly mention alternatives or when not to use it, the context is strong enough given the sibling names. No exclusions are stated, but the use case is obvious.

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

Deploy Server

Other Tools